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.converge)<a href="https://agentmods.dev/commands/ambystechcom/ambykit/amby.converge"><img src="https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.converge/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.converge"><img src="https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.converge.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.00022 | $0.00513 |
| Opus 5.5 | $0.00009 | $0.00205 |
| Sonnet 5.5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
amby.converge 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/.
Converge feature $ARGUMENTS (default: the current feature): does the code satisfy its artifacts?
Never edit source code — only that feature's tasks.md and spec.md are writable.
- No
tasks.md→ stop, say to run/amby.tasks. Noplan.md→ converge on spec + tasks and say so. - For every
FR-###/SC-###, plan decision (incl.data-model.md/contracts/), and checkedT###: look for evidence only in files the plan/tasks name. Classify covered, gap (absent), or unverified (inconclusive). Skip items the plan marks deferred/out of scope. - Append, don't rewrite. Under
## Convergenceintasks.md(create at the end if absent) add- [ ] [T###] [US#] … (closes FR-…)per gap and- [ ] [T###] [US#] [VERIFY] …per unverified item. Continue IDs from the highestT###anywhere in the file; skip items already listed unchecked there. Nothing to add → leave the file untouched. - In
spec.md, patch onlystatus:lines: a story →donewhen every FR/SC it maps to is covered; the feature →donewhen all stories are. - Report: converged (no gaps) or gaps found (N), counts per class, and a table of every ID with its class and a one-line reason for each gap/unverified item.
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 · 22 tokens per session scan A a05c14e17d3f
amby.converge is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 513 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
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
review
A command for reviewing code with security checks and a check for compliance with MX tags. The available description does not explain what MX tags are.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
differential-audit
Audit EARS↔code coherence via a bidirectional differential. With no arguments, opens a scoping conversation that interprets what the user wants audited, maps it to arrows, and captures an explicit EARS selection. With one or more EARS IDs, audits those specs directly using configured defaults. Requires docs/arrows/…
revisar
Peer review estricto de código con análisis de rendimiento, arquitectura, seguridad y cumplimiento. Usa cuando el usuario dice "revisar código", "code review", "peer review", "revisame este archivo", "review my code", "analizar código", "revisar PR", "revisar feature". Incluye análisis de performance, security OWASP…
reversa
Extraer arquitectura de un codebase existente (ingeniería inversa).