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/status)<a href="https://agentmods.dev/commands/kossakovsky/cc-plugins/status"><img src="https://agentmods.dev/badge/commands/kossakovsky/cc-plugins/status/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/status"><img src="https://agentmods.dev/badge/commands/kossakovsky/cc-plugins/status.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.00010 | $0.00368 |
| Opus 5.5 | $0.00004 | $0.00147 |
| Sonnet 5.5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade B, and why
status 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **Read** `~/.claude/settings.json` using the Read tool What it actually says
Provider Status
Show the current AI provider configuration.
Steps
-
Read
~/.claude/settings.jsonusing the Read tool -
Determine current provider by checking
env.ANTHROPIC_BASE_URL:- Not set or missing → Anthropic (native)
- Contains
z.ai→ Z.AI - Contains
moonshot→ Kimi - Contains
minimax→ MiniMax - Other → Custom (show the URL)
-
Display the following information:
- Provider: name of the current provider
- Base URL: value of
ANTHROPIC_BASE_URL(or "native" if not set) - Opus model: value of
ANTHROPIC_DEFAULT_OPUS_MODEL(or "default" if not set) - Sonnet model: value of
ANTHROPIC_DEFAULT_SONNET_MODEL(or "default" if not set) - Haiku model: value of
ANTHROPIC_DEFAULT_HAIKU_MODEL(or "default" if not set) - Small/fast model: value of
ANTHROPIC_SMALL_FAST_MODEL(or "default" if not set) - API key: show first 8 characters + "..." if
ANTHROPIC_AUTH_TOKENis set, or "not set"
-
Check saved keys: Read
~/.claude/provider-keys.jsonif it exists, and list which providers have saved keys (just the provider names, not the keys themselves)
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 · 30 lines · 10 tokens per session scan B a8fc0b7dd7ed
status is a command published in the GitHub repository kossakovsky/cc-plugins (3 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 368 once invoked, about $0.0000 per session on Opus 5.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-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.
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.