claude-token-saver@3.11.2
Renamed to sprag-cli. This name stopped receiving updates at 3.55.0; install sprag-cli for current releases: npm uninstall -g claude-token-saver && npm i -g sprag-cli
Route the easy work your expensive Claude model keeps repeating down to haiku/sonnet — post-hoc session analysis, no realtime router, no extra LLM calls.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic install modifies Claude Code integration files and registers package commands, creating a guarded first-party extension lifecycle risk. The inspected source does not establish concrete malicious behavior, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The postinstall hook automatically runs the CLI install command.
- That command installs a package-owned Claude Code skill, status line, and session and prompt hooks.
- The installer writes Claude Code settings and adds package commands to its hooks.
- The setup has no confirmation prompt; its writes are limited to this package’s integration and preserve unrelated hook entries.
- The inspected install behavior is first-party Claude Code integration setup; no credential collection, unrelated network recipient, or payload execution was identified.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to claude-token-saver@3.11.2.
See all versions of claude-token-saver for other recorded verdicts.
- Review the evidence and your use of claude-token-saver@3.11.2 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.