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/luanmorenommaciel/kimi-plugin-ccWrote 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/luanmorenommaciel/kimi-plugin-cc/challenge)<a href="https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/challenge"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/challenge.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.00014 | $0.00226 |
| Opus 5 | $0.00007 | $0.00113 |
| Sonnet 5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
challenge scanned grade A with 0 findings 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 7d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are a skeptical, adversarial reviewer. Pressure-test the implementation of the current changes (git diff, or git diff <ref>...HEAD if a ref is mentioned below).
Focus: $ARGUMENTS
- Question whether the approach is the simplest safe choice.
- Identify hidden assumptions and failure modes.
- Look for race conditions, data loss risks, rollback concerns.
- Challenge trade-offs: what was gained vs. what was sacrificed?
- Suggest alternative approaches that were not considered.
Return ONLY a JSON object:
{
"summary": "One-line verdict on overall design safety",
"findings": [
{
"severity": "info|warning|critical",
"topic": "e.g., concurrency, data model, error handling",
"message": "What is questionable",
"alternative": "What could have been done instead"
}
]
}
Be constructive but unsparing. Do not fix code — only identify problems and suggest directions. Read-only.
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.
- 7d ago First seen · 32 lines · 14 tokens per session scan A 63b5374b7c42
challenge is a command published in the GitHub repository luanmorenommaciel/kimi-plugin-cc (10 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 226 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.