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/mode)<a href="https://agentmods.dev/commands/akka/ai-marketplace/mode"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/mode/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/mode"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/mode.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.00023 | $0.01529 |
| Opus 5.5 | $0.00009 | $0.00612 |
| Sonnet 5.5 | $0.00005 | $0.00306 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
mode scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
platform (`winget upgrade Akka.Cli`, `brew upgrade akka`, or the curl How it starts
The opening of the file, as written. The whole thing — 122 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:mode shows the project's conformance mode, or sets it. The mode is
recorded in .akka/exit-conditions.yaml and controls exactly one thing:
whether unmet exit conditions block shipping.
- À la carte — the default. The exit-condition set is dormant until the
developer asks for it: only the Akka-intrinsic baseline resolves, no auditors
are created, and nothing is captured. Once asked for, conditions are checked
and shown but never block
/akka:ship, which proceeds with an explicit override. - Enforced — the full set applies from the start.
/akka:shiprefuses to release until every applicable condition isgreenand not stale, or covered by an effective waiver. You use sign-off, strike, and waive to resolve eachopenorredcondition first.
Every Specify command is available in both modes; the mode changes what the
engine does on its own, not the command set. In Enforced mode the process gates
PROC-AUDITOR-COVERAGE and PROC-ADEQUACY-REVIEWED apply as usual. While the
set is dormant they do not resolve at all — there is nothing yet to have
covered or reviewed.
The organization can constrain this. A policy may set a different default and lock it; when the mode is locked, only the org-allowed mode(s) may be set. A locked Enforced mode cannot be dropped to À la carte to bypass the ship gate.
Outline
-
Parse the argument from
$ARGUMENTS. Three cases:- Empty — this is a query. Skip to step 2 with no argument.
enforcedora-la-carte— pass through unchanged.- A recognizable spelling of à la carte — the documentation renders the
mode as "À la carte", so accept
alacarte,a la carte,à-la-carte, andà la carteand normalize them toa-la-cartebefore calling the CLI. The CLI accepts only the two canonical spellings.
Anything else: stop and tell the user "
/akka:modetakesenforcedora-la-carte, or no argument to show the current mode." Do not call the CLI.
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 · 122 lines · 23 tokens per session scan A 9c16094c53fc
mode is a command published in the GitHub repository akka/ai-marketplace (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,529 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
land
Resolve and squash merge one named, currently authorized pull request.
release
Prepare and publish spec-driven-steroids through the tag-triggered npm release pipeline.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.