claude-token-saver@3.24.0
renamed to sprag-cli - same tool, same releases. Switch with: 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 postinstall hook automatically invokes setup that writes persistent Claude Code skill and hook configuration before any consent gate. This meets the policy for blocking unconsented install-time mutation of an AI-agent control surface.
Decision evidence
public snapshot- package.json runs the CLI install command automatically during postinstall.
- The install command calls installAll before any consent prompt can gate that call.
- installAll writes an auto-trigger skill and configures statusline, SessionStart, and UserPromptSubmit hooks.
- The CLI describes the skill as making Claude respond automatically to matching user wording.
- No source evidence inspected establishes credential theft, external exfiltration, or remote payload execution.
Source & flagged code
8 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.24.0.
See all versions of claude-token-saver for other recorded verdicts.
- Avoid installing claude-token-saver@3.24.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.