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/status)<a href="https://agentmods.dev/commands/akka/ai-marketplace/status"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/status/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/status"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/status.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.00030 | $0.00908 |
| Opus 5 | $0.00015 | $0.00454 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
status 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 9d 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 — 87 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).
Purpose
/akka:status prints the current definition-of-done manifest: every exit
condition grouped by Definition-of-Done type, with its state (open, green,
or red), its properties (provenance, waiver, applicability), and any open
reason. The two locked process-integrity gates, PROC-AUDITOR-COVERAGE and
PROC-ADEQUACY-REVIEWED, appear among the conditions like any other.
The manifest reflects the project's own state — waived, struck, and signed-off
conditions appear as such — so it agrees with /akka:conform.
Status never runs an auditor. It does not build, test, lint, or probe. That
is the whole difference from /akka:conform: machine-checkable conditions stay
open here until conform evaluates them. Once conform has run, the two agree.
Because it changes nothing and costs nothing, status is the command to reach for during an autonomous build — it shows progress without interrupting the machine.
Outline
-
Render the manifest. Call
akka_ec_statusfor the project directory. This resolves the exit-condition library against the org governance floor and the project's own strikes, waivers, and sign-offs, then renders the manifest. It is read-only and runs no auditors. -
Get the counts. Call
akka_ec_rollupfor the same directory. It returns the status counts by tier and by Definition-of-Done type as JSON. Use this as the headline so the user sees the shape of the build before the detail. -
Report plainly. Lead with the rollup: how many conditions are settled, how many are waiting on the user, how many are blocked outside the project. Then surface the conditions that are
openorred, each with its user-facing reason — the reason field is the action.State plainly that the auditors were not run, and that the machine-checkable conditions are therefore still
openrather than failing. Do not present an unevaluated condition as a problem. Offer/akka:conformas the way to resolve them.
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.
- 9d ago First seen · 87 lines · 30 tokens per session scan A 283e9a7f576a
status is a command published in the GitHub repository akka/ai-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 908 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
sddp-devsetup
Command description: Analyze the repo and recommend local development setup. Argument hint: [optional specific environment constraints or preferences] Command category: environment Prerequisites: none.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
approve-proposed
Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block. Single-command idiom that closes the two-step latency in ADR-0001's PROPOSED-by-default contract; the user reviews proposals in Ask/Plan mode, then runs this once to write all of them. Use when the prior…
stack-currency-check
Verify that the patterns the model is about to use for a given framework+version are current per official docs, and cache the result as CURRENTPATTERNS.md at the project level. Prevents the "gold-standard audit" anti-pattern where training-data defaults ship outdated patterns (e.g. Supabase getSession when getUser is…
apply-sweep-triage
Persist the user's triage decisions (apply, decline, discuss) from a SWEEP snapshot into REVIEWPREFERENCES.md so future sweeps suppress declined findings and track applied fixes. Use after the user has edited the triage values in a SWEEP snapshot file produced by repo-consistency-sweep. Do not use when no sweep…
concise
Toggle a project-local concise-output directive that suppresses agent prose padding during SDD steps. State lives in the project's agent memory file (AGENTS.md preferred when present, else CLAUDE.md / GEMINI.md / .cursor/rules / .windsurf/rules / etc.) inside a clearly marked block, so it is reversible and reviewable.