What is amby.converge?

A code-review command that checks whether implemented work matches its specification, plan, and task list. It records missing or uncertain work as new tasks and does not edit source code.

Use it after implementing a feature to review listed requirements, decisions, and checked tasks, then update the project’s task and specification files.

It exposes unfinished requirements without changing the implementation, so gaps can be addressed before the feature is considered complete.

amby.converge — Command for Claude Code by ambystechcom: A code-review command that checks whether implemented work matches…

Install

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.

agentmods

npx agentmods add commands/ambystechcom/ambykit/amby.converge

Clone the repo

git clone --depth 1 https://github.com/ambystechcom/AmbyKit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.converge.svg)](https://agentmods.dev/commands/ambystechcom/ambykit/amby.converge)

Your own site

<a href="https://agentmods.dev/commands/ambystechcom/ambykit/amby.converge"><img src="https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.converge.svg" alt="Measured on agentmods" height="20"></a>

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 513 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00011	$0.00257
Sonnet 5	$0.00004	$0.00103
Haiku 4.5	$0.00002	$0.00051

Measured 5d ago against content hash a05c14e17d3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 5d 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.

.claude/commands/amby.converge.md · 25 lines

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. No plan.md → converge on spec + tasks and say so.
For every FR-###/SC-###, plan decision (incl. data-model.md/contracts/), and checked T###: 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 ## Convergence in tasks.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 highest T### anywhere in the file; skip items already listed unchecked there. Nothing to add → leave the file untouched.
In spec.md, patch only status: lines: a story → done when every FR/SC it maps to is covered; the feature → done when 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.

Changes

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.

5d ago First seen · 25 lines · 22 tokens per session scan A a05c14e17d3f

Subscribe to this mod's changes

amby.converge is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 513 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.

Code review agent-skills agentic-coding agentic-workflow ai-coding ai-tools spec

amby.converge

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

oss-docs

release-update

github

release

harness

e2e