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.
npx agentmods add commands/kanopi/cms-planner/overviewgit clone --depth 1 https://github.com/kanopi/cms-plannerWhat 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 | $0.00000 | $0.00873 |
| Opus 5 | $0.00000 | $0.00436 |
| Sonnet 5 | $0.00000 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
overview 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 yesterday.
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.
The source is not reproduced here
Licensed GPL-2.0
The repository is licensed GPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- yesterday First seen · 153 lines · 0 tokens per session scan A bb3376ec77ab
overview is a command published in the GitHub repository kanopi/cms-planner (1 stars, last pushed 5mo ago), licensed GPL-2.0. It costs nothing until one of its globs matches a file; then it loads 873 tokens. 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
todo
Manages the project's TODO backlog with inline markers in docs reconciled against a central, impact-ordered list, optionally mirrored to a task MCP.
triage
Triages an unprioritized list of bugs, debt, and tasks into a full MoSCoW breakdown with justification and an attack order.
roadmap-suggest
Mine the repo for new roadmap items — or, on a fresh project, bootstrap the board from scratch.
triage
Promote ideas from Ideas.md into Epics or User Stories in the Epic backlog (dedup, typed ID, voice).
detail-us
Detail one User Story to Ready (As a/I want/So that + Gherkin AC + estimate + layer + deps).
ledger-check
Audit all ledger files for drift (report; fix only on request).