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/jayminwest/kotadb/toolsgit clone --depth 1 https://github.com/jayminwest/kotadbWhat 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.00290 |
| Opus 5 | $0.00000 | $0.00145 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
tools 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 2d 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
/tools
Template Category: Action Prompt Level: 4 (Contextual)
Catalog repository tooling for quick agent reference. No arguments required.
Steps
- Git prep:
git fetch --all --prune,git pull --rebase, confirm clean tree (git status --short), and stay ondevelop(read-only task) while noting that active work branches (feat/,bug/,chore/, etc.) merge intodevelopbefore promotion tomain. - Review documentation: scan
README.md,CLAUDE.md,adws/README.md, and workflow specs for tooling mentions (Bun, Biome, Playwright, Docker, etc.). - Inventory commands: list scripts from
package.json, automation helpers underadws/**, and supporting binaries (uv, gh, sqlite3). - Produce catalog: document tools as TypeScript-style signatures with concise comments, e.g.,
bun run typecheck(): Promise<void> // TypeScript gate. - Validate: ensure the list is comprehensive, deduplicated, and reflects current versions/usage.
Reporting
- Tool catalog (signatures + comments) stored in the agreed location (e.g.,
docs/tooling.md). - Summary of sources consulted and any missing/optional tools.
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.
- 2d ago First seen · 18 lines · 0 tokens per session scan A 9f961cf4e1ee
tools is a command published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 290 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-30.
Other commands, from other repositories
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
validate-dependencies
Validate all task dependencies for issues.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.