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/akka/ai-marketplaceWrote 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/akka/ai-marketplace/converge)<a href="https://agentmods.dev/commands/akka/ai-marketplace/converge"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/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/akka/ai-marketplace/converge"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/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.00035 | $0.02376 |
| Opus 5 | $0.00017 | $0.01188 |
| Sonnet 5 | $0.00007 | $0.00475 |
| Haiku 4.5 | $0.00003 | $0.00238 |
Grade A, and why
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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Goal
Close the gap between what a feature's specification, plan, and tasks call for and what the
codebase currently implements. Read spec.md, plan.md, and tasks.md as the sole
source of intent (with the constitution as governing constraints), assess the current
state of the code, determine which requirements, acceptance criteria, plan decisions, and
existing tasks are unmet, incomplete, or only partially satisfied, and append each piece
of remaining work as a new, traceable task at the bottom of tasks.md so that
/akka:implement can complete it. This command MUST run only after
/akka:implement has run on the current tasks.md, and after
/akka:tasks has produced a complete tasks.md.
This is not a diff tool and does not track changes. It assesses the present state of the code relative to the feature's artifacts — no git, no branch comparison, no history.
Operating Constraints
APPEND-ONLY, NEVER REWRITE: The command's only write is appending a new
## Phase N: Convergence section to tasks.md. It MUST NOT:
- modify
spec.mdorplan.mdin any way; - rewrite, renumber, reorder, or delete any existing task (including tasks from a prior Convergence phase);
- modify, create, or delete any application code — completing the appended tasks is the
job of
/akka:implement.
When the codebase already satisfies everything, the command MUST leave tasks.md
byte-for-byte unchanged (no empty Convergence header) and report a clean result.
Constitution Authority: The project constitution (loaded via akka_sdd_constitution)
is non-negotiable. Code that violates a MUST principle is the highest-severity finding
and produces a corresponding remediation task. If the constitution is an unfilled template
or unavailable, skip constitution checks gracefully rather than failing.
Execution Steps
1. Initialize Convergence Context
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.
- 11d ago First seen · 217 lines · 35 tokens per session scan A 99e88f87fe2b
converge is a command published in the GitHub repository akka/ai-marketplace (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 2,376 once invoked, about $0.0002 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
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.
autospec.plan
Generate YAML implementation plan from feature specification.
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
devs-team
Parallel multi-lens critique of a solution design (the active spec if present, else the decision brief). Dispatches 5 engineering lenses, merges findings, reports a verdict. Report-only, never blocks.