Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ww-w-ai/super-token-saver/plugin install super-token-saverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ww-w-ai/super-token-saver/setup-git-lite)<a href="https://agentmods.dev/skills/ww-w-ai/super-token-saver/setup-git-lite"><img src="https://agentmods.dev/badge/skills/ww-w-ai/super-token-saver/setup-git-lite.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.01013 |
| Opus 5 | $0.00021 | $0.00507 |
| Sonnet 5 | $0.00008 | $0.00203 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade B, and why
setup-git-lite scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| `install` | 🔴 destructive | ❌ user-only | Modifies ~/.claude/settings.json + shell profile. Requires explicit `<command-name>super-token-saver:setup-git-lite</command-name>` tag with `<command-args>install</command-ar How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Claude Code's built-in includeGitInstructions token consumption.
Subcommand routing
Parse the first argument from $ARGUMENTS:
| Subcommand | Risk | AI-allowed | Behavior |
|---|---|---|---|
install |
🔴 destructive | ❌ user-only | Modifies ~/.claude/settings.json + shell profile. Requires explicit <command-name>super-token-saver:setup-git-lite</command-name> tag with <command-args>install</command-args> |
revert |
🔴 destructive | ❌ user-only | Aggressive cleanup. Same gating as install |
status |
🟢 safe | ✅ allowed | Read-only diagnostic |
dismiss-banner |
🟢 safe | ✅ allowed | Suppresses the recommendation banner (preferences.json flag) |
undismiss-banner |
🟢 safe | ✅ allowed | Re-enables the banner |
help |
🟢 safe | ✅ allowed | Prints usage |
| (empty) | 🟢 safe | ✅ allowed | Run status, then append one-line usage hint: "Subcommands: install, revert, status, dismiss-banner, undismiss-banner, help" |
Invocation guard — enforce for destructive subcommands only
If the subcommand is install or revert:
-
Verify explicit invocation: the triggering user message MUST contain
<command-name>super-token-saver:setup-git-lite</command-name>along with<command-args>install</command-args>(orrevert). If these tags are absent (i.e., you inferred the intent from natural-language context), STOP and respond:"This action modifies your global Claude Code settings and shell profile. Please invoke explicitly by typing
/setup-git-lite install(orrevert)." -
User confirmation before execution: even when the tag is present, print a one-line summary and ask for a literal "yes":
"Install will:
- Set
includeGitInstructions: falsein ~/.claude/settings.json - Append a marker block to your shell profile exporting CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 Proceed? (type yes to confirm)"
Only proceed on a literal
yes. Any other response — cancel. - Set
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 80 lines · 42 tokens per session scan B f0179dbec5c8
setup-git-lite is a skill published in the GitHub repository ww-w-ai/super-token-saver (31 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 1,013 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git-workflow
Use when starting feature work that needs a branch, creating worktrees for isolation, making atomic commits during development, or completing a development branch via merge, PR, preserve, or discard. Also use when the user says "set up worktree", "create PR", "finish this branch", "start feature", or when you need an…
shipyard-verification
Use when about to claim work is complete, fixed, or passing — before committing, creating PRs, or moving to the next task. Also use when you catch yourself using words like "should", "probably", or "seems to" about work state, or when expressing satisfaction ("Great!", "Done!") before running verification commands.…
shipyard-ship
Use when delivering or releasing a completed Shipyard phase under Codex — final verification, pre-ship security audit, documentation, and release. Trigger when the user says "ship it", "ship this phase", "release this", "we're done — finalize", or "run the shipyard ship workflow". This is the Codex inline-sequential…
pith-commit
One-shot commit message generator. Conventional Commits format, subject ≤50 chars. Use when writing a git commit message for staged changes. Does not persist.
sw-ship
Ships the current work unit. Verifies all gates passed, creates a PR with evidence-mapped body, updates workflow state to shipped.
sw-sync
Syncs the local repository by fetching all remotes, updating the base branch, and removing stale local branches that are not protected by live sessions or helper worktrees.