reliability

reliability is a command for Claude Code from akka/ai-marketplace. It costs 23 tokens per session (2,706 once invoked), scanned A, original, Apache-2.0.

A command that configures resilience testing for an Akka service by discovering its endpoints and writing a configuration file for a local testing dashboard. Resilience testing checks how a service behaves under failures or disruption.

In plain words
What is it for?
Use it to attach a service to the local resilience dashboard, or remove its `.akka/reliability.yml` configuration.
Why use it?
It connects the running service to the testing dashboard without generating testing code inside the project.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

Part of the akka plugin — 12 skills, 9 commands, 1 MCP server shipped together

Good fit Use it to attach a service to the local resilience dashboard, or…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/akka/ai-marketplace/reliability
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.

Clone the repo
git clone --depth 1 https://github.com/akka/ai-marketplace

Made for: Claude Code.

Or install akka, the plugin that ships this one along with the rest of its 12 skills, 9 commands, 1 MCP server.

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.

agentmods badge for reliability

README.md
[![agentmods](https://agentmods.dev/badge/commands/akka/ai-marketplace/reliability.svg)](https://agentmods.dev/commands/akka/ai-marketplace/reliability)
Your own site
<a href="https://agentmods.dev/commands/akka/ai-marketplace/reliability"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/reliability.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,706 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.02706
Opus 5 $0.00012 $0.01353
Sonnet 5 $0.00005 $0.00541
Haiku 4.5 $0.00002 $0.00271

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

Security

Grade A, and why

reliability 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 6d 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.

plugins/akka/commands/reliability.md · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 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). If the input contains the word "remove", execute the Remove Workflow. Otherwise, execute the Attach Workflow.

Required MCP Capabilities

This command requires the following MCP tools. If any are unavailable, stop and tell the user to update the Akka CLI and restart Claude Code.

  • Local development: akka_local_start, akka_local_run_service, akka_local_cluster_status, akka_local_status
  • Service introspection: akka_backoffice_list_components, akka_backoffice_discovery

Purpose

This command sets up resilience testing for an Akka service. It discovers the service's endpoints at runtime via backoffice MCP tools and writes a .akka/reliability.yml config file. The daemon (port 9889) reads this config and serves a self-contained testing dashboard — no code is generated in the user's project.

Two modes:

  • Attach (default): ensure cluster is running, discover endpoints, write config, report dashboard URL
  • Remove: delete .akka/reliability.yml (and any legacy artifacts)

The dashboard is served by the daemon at http://localhost:9889/resilience/ and provides:

  • Single-shot READ/WRITE operations against the service
  • Burst load testing with configurable duration, interval, and read ratio
  • Real-time latency chart and transaction log via SSE
  • Cluster node management (stop/start nodes 2–3 to test failover)

Attach Workflow

Step 0 — Ensure cluster is running

  1. Call akka_local_status to check if the daemon is running.
  2. If not running: call akka_local_start with postgres: true.
  3. Check if a service is running. If not: call akka_local_run_service with nodes: 3 to start a 3-node local cluster.
  4. Call akka_local_cluster_status to verify nodes are up.
  5. If the cluster fails to start, check akka_local_logs with source: "service" for errors and report to the user.

Step 1 — Discover endpoints via backoffice

Read the full file on GitHub · 271 lines

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.

  1. 6d ago First seen · 271 lines · 23 tokens per session scan A fbed3ef50724

Subscribe to this mod's changes

reliability is a command published in the GitHub repository akka/ai-marketplace (6 stars, last pushed 7d ago), licensed Apache-2.0. It adds 23 tokens to every session and 2,706 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.