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.constitutiongit 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.00013 | $0.00245 |
| Opus 5 | $0.00006 | $0.00122 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
amby.constitution 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.
What it actually says
Establish or update the project constitution at .amby/constitution.md.
- If the file is missing, create it from
@.amby/templates/constitution.mdand fill it in. If it exists, amend only the section relevant to$ARGUMENTS(or, with no argument, review all principles briefly). - Interview the user only where a principle is unclear — ask one focused question at a time.
- Keep each principle short, imperative, and numbered so later phases can cite it.
- Cover: code quality, testing standards, UX consistency, performance/reliability, security. Add project-specific non-negotiables as needed.
- Bump the version and update the date. Do not restate feature requirements — those belong in specs.
Output only the edited constitution. Be concise.
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 · 19 lines · 13 tokens per session scan A 4cf304faad72
amby.constitution is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 245 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.