Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/AlexPl292/awesome-claude-spinnersWrote 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/commands/alexpl292/awesome-claude-spinners/install-spinner)<a href="https://agentmods.dev/commands/alexpl292/awesome-claude-spinners/install-spinner"><img src="https://agentmods.dev/badge/commands/alexpl292/awesome-claude-spinners/install-spinner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/alexpl292/awesome-claude-spinners/install-spinner"><img src="https://agentmods.dev/badge/commands/alexpl292/awesome-claude-spinners/install-spinner.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00343 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade B, and why
install-spinner 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 11d 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.
Once the user has chosen a pack, read the corresponding file from `spinners/<pack-name>.json`. Then read the user's `~/.claude/settings.json` file. What it actually says
Ask the user which spinner pack they want to install. List all available .json files from the spinners/ directory in this repository (without the .json extension).
Present the packs to the user in a table with three columns: Pack name, a short description, and a couple of example verbs. Use the table from README.md as reference for descriptions and examples.
Let the user pick one.
Once the user has chosen a pack, read the corresponding file from spinners/<pack-name>.json. Then read the user's ~/.claude/settings.json file.
Each spinner file has this format:
{
"spinnerVerbs": {
"mode": "replace",
"verbs": ["Phrase 1", "Phrase 2"]
}
}
Copy the spinnerVerbs field from the chosen spinner file into ~/.claude/settings.json. If the spinnerVerbs field already exists in settings.json, replace its value. If it doesn't exist, create it.
IMPORTANT: Do not modify any other fields in settings.json. Only change spinnerVerbs.
After successful installation, print:
Spinner pack "<pack-name>" installed successfully!
No need to restart Claude Code — the new spinners are active immediately.
Removing spinners
If the user asks to remove or reset spinners, read ~/.claude/settings.json and delete the spinnerVerbs field entirely. Do not modify any other fields. After removal, print:
Spinner pack removed. Default spinners are back.
No need to restart Claude Code — the change takes effect immediately.
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.
- 11d ago First seen · 39 lines · 0 tokens per session scan B 48ab4e1683ad
install-spinner is a command published in the GitHub repository AlexPl292/awesome-claude-spinners (75 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 343 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.