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.
npx agentmods add commands/akka/ai-marketplace/docsgit 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/docs)<a href="https://agentmods.dev/commands/akka/ai-marketplace/docs"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/docs.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.03832 |
| Opus 5 | $0.00013 | $0.01916 |
| Sonnet 5 | $0.00005 | $0.00766 |
| Haiku 4.5 | $0.00003 | $0.00383 |
Grade A, and why
docs 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.
How it starts
The opening of the file, as written. The whole thing — 267 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:docs is a generator. It writes and refreshes the project's rendered
documentation under docs/, then hands that output to the content-governance
exit-condition family that verifies it. Documentation is a surface class in the
single coverage gate: every documentable thing needs a page, the same way every
code module needs a covering check. Generation lives here in the assistant; the
engine verifies the deterministic conditions and records the attestation for the
one condition it cannot decide.
When it runs
/akka:docs is primarily an À la carte command. The developer invokes it
directly when they want to (re)generate the project's rendered documentation
and see how the content-governance exit conditions decided. In Enforced mode
the assistant runs the same activity autonomously as part of its build loop,
whenever CONTENT-LANGUAGE, Completeness, or CONTENT-TONE is open and the
assistant can act on it. In both modes the behavior is identical; only
ship-gating differs.
Outline
-
Enumerate the documentable things. Collect what the project can document from observable sources — the a-la-carte commands, the active exit conditions, the public API endpoints detected in the tree. This enumerable set is the completeness target.
-
Load the fixed template. Read
plugins/akka/templates/docs-template.htmlfrom the akka plugin. This file is the fixed design contract for/akka:docs: it contains the full CSS, the full HTML skeleton, the header, the stats grid, the collapsible diagram and component sections, the SVG scaffolding for the interaction diagram, and the banded SVG scaffolding for the component graph. Every generateddocs/index.htmluses this template verbatim — the assistant MUST NOT modify the CSS, the layout, the fonts, the colors, or any other design detail. Customers do not override the design; the template is the design. The palette is enumerated inplugins/akka/templates/akka-style-guide.md, and step 9 checks the generated page against it, so this rule is enforced rather than trusted.
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 · 267 lines · 26 tokens per session scan A 424e9a766a9b
docs is a command published in the GitHub repository akka/ai-marketplace (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 26 tokens to every session and 3,832 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.
Other commands, from other repositories
spec-kitty.implement
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.
bench-capture
Score the 2 bench variant folders for one size (build/acceptance/regression/conventions/capture + rubric + cross-solution review), record, report, and reset.
autospec.plan
Generate YAML implementation plan from feature specification.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.