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 skills add akka/ai-marketplace --skill reliabilitygit 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/skills/akka/ai-marketplace/reliability)<a href="https://agentmods.dev/skills/akka/ai-marketplace/reliability"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/reliability/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/skills/akka/ai-marketplace/reliability"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/reliability.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.00027 | $0.02603 |
| Opus 5 | $0.00014 | $0.01301 |
| Sonnet 5 | $0.00005 | $0.00521 |
| Haiku 4.5 | $0.00003 | $0.00260 |
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 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
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
- Call
akka_local_statusto check if the daemon is running. - If not running: call
akka_local_startwithpostgres: true. - Check if a service is running. If not: call
akka_local_run_servicewithnodes: 3to start a 3-node local cluster. - Call
akka_local_cluster_statusto verify nodes are up. - If the cluster fails to start, check
akka_local_logswithsource: "service"for errors and report to the user.
Step 1 — Discover endpoints via backoffice
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 · 255 lines · 27 tokens per session scan A 062c55c225f3
reliability is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 2,603 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 skills, from other repositories
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
gsd-verify-work
Validate built features through conversational UAT.
gsd-eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
gsd-audit-uat
Cross-phase audit of all outstanding UAT and verification items.
tdd
Test-driven development with red-green-refactor loops around vertical slices (tracer bullets), not horizontal layers. Use when asked to "use TDD", "write test-first", "red-green-refactor", "build this with tests", or when a feature has a clear observable contract. The discipline complement to the test/add-tests skills…