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/priivacy-ai/spec-kitty/spec-kitty.implementgit clone --depth 1 https://github.com/Priivacy-ai/spec-kittyWrote 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/priivacy-ai/spec-kitty/spec-kitty.implement)<a href="https://agentmods.dev/commands/priivacy-ai/spec-kitty/spec-kitty.implement"><img src="https://agentmods.dev/badge/commands/priivacy-ai/spec-kitty/spec-kitty.implement.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.00000 | $0.00016 |
| Opus 5 | $0.00000 | $0.00008 |
| Sonnet 5 | $0.00000 | $0.00003 |
| Haiku 4.5 | $0.00000 | $0.00002 |
Grade A, and why
spec-kitty.implement 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 today.
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
Legacy codex prompt for implement (pre-3.2.0)
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.
- today First seen · 2 lines · 0 tokens per session scan A 1d63a714287c
spec-kitty.implement is a command published in the GitHub repository Priivacy-ai/spec-kitty (1,586 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 16 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-09-03.
Other commands, from other repositories
speckit.taskstoissues
When executing this command, delegate independent work to parallel sub-agents to reduce total execution time.
status
Run /status — see .claude/commands/status.md for the authoritative spec.
taskstoissues
tasks.md を課題トラッカー用の issue ドラフトに変換する（既定はゼロ依存の Markdown 出力）.
status
specs/ 全体を走査し、各機能の進捗（spec/plan/tasks/実装）を一覧化する.
progress
Run the workflow in docs/playbooks/progress.md: read PROJECT.md, docs/progress.md, and the actual repo (trust the repo over the doc). Locate me, name concrete progress, append a dated session-log entry, propose the single next action, and check docs/learning-debt.md for anything worth pulling in. If I seem stuck…
implement
tasks.md のタスクを依存順に一つずつ実装する.