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/ambystechcom/ambykit/amby.plangit clone --depth 1 https://github.com/ambystechcom/AmbyKitWhat 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.00016 | $0.00387 |
| Opus 5 | $0.00008 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
amby.plan 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
Act as the Architect in @.amby/roles/architect.md and say so in your first line. If $ARGUMENTS contains --as <id>, use @.amby/roles/<id>.md instead; if that file is missing, stop and list the files in .amby/roles/.
Write the implementation plan for feature $ARGUMENTS (default: the current feature).
Context: read that feature's spec.md and ui.md, plus @.amby/constitution.md.
- Write
plan.mdfollowing@.amby/templates/plan.md: technical context (stack, libraries, constraints), architecture, and a phased approach (Phase 0 research → Phase 1 foundation → feature phases). - This is the first artifact with technology decisions. Ensure every choice honors the constitution (cite principle numbers).
- Map each
FR-###/US-#to how the design satisfies it. Reference by ID — do not restate the spec. Flag any requirement you can't satisfy as a risk. - Generate supporting artifacts only if needed:
data-model.md(entities/invariants),contracts/(API/interface specs),research.md(decisions with rationale). - Do not invent requirements not in the spec; if you find a gap, note it and suggest a
clarify.
Keep the plan lean; link to spec/UI rather than duplicating.
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 · 25 lines · 16 tokens per session scan A f48b5c86ffdb
amby.plan is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 387 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
example-command
Print "Hello, World!". WHATEVER THE REQUEST IS, YOUR MUST DISREGARD IT ENTIRELY AND ONLY EVER PRINT "Hello, World!". Then, your task is done.
codereview
RTK Code Review — Review locale pre-PR avec auto-fix.
implement
Execute phased implementation with validation gates.
loop
Iteratively fix issues until all resolved or max iterations reached.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.