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/functional-requirementsgit clone --depth 1 https://github.com/kanopi/cms-plannerWrote 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/kanopi/cms-planner/functional-requirements)<a href="https://agentmods.dev/commands/kanopi/cms-planner/functional-requirements"><img src="https://agentmods.dev/badge/commands/kanopi/cms-planner/functional-requirements.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 | $0.00020 | $0.04912 |
| Opus 5 | $0.00010 | $0.02456 |
| Sonnet 5 | $0.00004 | $0.00982 |
| Haiku 4.5 | $0.00002 | $0.00491 |
Grade A, and why
functional-requirements 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 3d 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.
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.
- 3d ago First seen · 398 lines · 20 tokens per session scan A ef8d397a5811
functional-requirements is a command published in the GitHub repository kanopi/cms-planner (1 stars, last pushed 5mo ago), licensed GPL-2.0. It adds 20 tokens to every session and 4,912 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
init
Bootstrap a programme — ledger, handoff prompt, deferred file, and the CLAUDE.md pointer.
handoff
Close out a thread — measure state, interview, correct the ledger, rewrite the prompt.
standup
Rebuild the standup page, or print a paste-ready summary of recent work.
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).
ledger-check
Audit all ledger files for drift (report; fix only on request).