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/kossakovsky/cc-pluginsWrote 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/kossakovsky/cc-plugins/setup)<a href="https://agentmods.dev/commands/kossakovsky/cc-plugins/setup"><img src="https://agentmods.dev/badge/commands/kossakovsky/cc-plugins/setup/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/kossakovsky/cc-plugins/setup"><img src="https://agentmods.dev/badge/commands/kossakovsky/cc-plugins/setup.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.00007 | $0.00281 |
| Opus 5.5 | $0.00003 | $0.00112 |
| Sonnet 5.5 | $0.00001 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade B, and why
setup 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
5. **Set permissions** using Bash: `chmod 600 ~/.claude/provider-keys.json` What it actually says
Setup Provider Keys
Configure and save API keys for providers to ~/.claude/provider-keys.json.
Steps
-
Read existing keys from
~/.claude/provider-keys.jsonif the file exists (use Read tool, handle file not found gracefully) -
Determine which provider to configure:
- If an argument was provided (e.g.,
zai), configure that provider - If no argument, ask the user which provider(s) they want to configure. Options:
zai,kimi,minimax
- If an argument was provided (e.g.,
-
For each provider to configure:
- Ask the user for their API key
- Add or update the key in the keys object under the provider name
-
Write the updated keys to
~/.claude/provider-keys.json:{ "zai": "key-here", "kimi": "sk-key-here", "minimax": "key-here" } -
Set permissions using Bash:
chmod 600 ~/.claude/provider-keys.json -
Confirm which providers were configured and remind the user they can now switch with
/switch-provider:<provider>
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.
- 1mo ago First seen · 34 lines · 7 tokens per session scan B 6e6dc408c378
setup is a command published in the GitHub repository kossakovsky/cc-plugins (3 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 281 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.