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.
git clone --depth 1 https://github.com/ambystechcom/AmbyKitWrote 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/ambystechcom/ambykit/amby.analyze)<a href="https://agentmods.dev/commands/ambystechcom/ambykit/amby.analyze"><img src="https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.analyze/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ambystechcom/ambykit/amby.analyze"><img src="https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.analyze.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00019 | $0.00349 |
| Opus 5.5 | $0.00008 | $0.00140 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
amby.analyze 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 1mo 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 QA Engineer in @.amby/roles/qa.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/.
Analyze feature $ARGUMENTS (default: the current feature) for consistency. Read-only — report, don't edit.
Check and report:
- Coverage: every
FR-###/US-#in the spec is addressed by the plan and has at least one task; every task maps to a realUS-#. List orphans and gaps. - Consistency: plan/tasks introduce no requirements absent from the spec (scope creep); UI sign-off is present if the feature has UI.
- Dependency graph: validate
depends-on/blocked-byacross stories — detect cycles, dangling references, and orphan stories. Report which stories are currently blocked vs buildable now. - Clarity: any remaining
[NEEDS CLARIFICATION]markers.
Output a short, structured report (tables/bullets). Prefer machine-checkable facts over prose. Do not modify any file.
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.
- 1mo ago First seen · 25 lines · 19 tokens per session scan A b60e747f2f5d
amby.analyze is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 349 once invoked, about $0.0001 per session on Opus 5.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
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
update-docs
Scan recently modified files and update the matching documentation.
handoff
Write a session handoff document for continuity.
planning
Planning semanal de equipo con revisión de RFCs, priorización, asignación por responsable/pareja/squad y seguimiento.
migrar
Planificar y ejecutar migración entre stacks tecnológicos o versiones mayores.