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 skills/jhostalek/dotclaude/audit-reliabilitynpx skills add JHostalek/dotclaude --skill audit-reliabilitygit clone --depth 1 https://github.com/JHostalek/dotclaudeWrote 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/jhostalek/dotclaude/audit-reliability)<a href="https://agentmods.dev/skills/jhostalek/dotclaude/audit-reliability"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/audit-reliability.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.00092 | $0.03430 |
| Opus 5 | $0.00046 | $0.01715 |
| Sonnet 5 | $0.00018 | $0.00686 |
| Haiku 4.5 | $0.00009 | $0.00343 |
Grade A, and why
audit-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 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!cat "${CLAUDE_SKILL_DIR}/../shared/audit-workflow.md"
Run as the reliability dimension. Determine whether the system continues to meet its essential correctness, availability, durability, recovery, and operability contracts through faults, overload, change, and lifecycle transitions. Reliability is end-to-end behavior; do not reduce it to retries, health checks, redundancy, or a resilience library.
Work top-down
- Reconstruct intended service behavior from product flows, contracts, schemas, configuration, infrastructure, telemetry, tests, runbooks, and deployment artifacts. Identify essential and degradable capabilities, state and durability guarantees, dependency and ownership boundaries, lifecycle states, workload envelope, recovery objectives, and consequences of delay, duplication, loss, stale results, or unavailability.
- Build the failure model. Map synchronous and asynchronous paths across clients, processes, services, queues, storage, caches, third parties, regions, devices, and operators. Include crash, hang, slowdown, partition, corruption, overload, quota, clock, configuration, deployment, and human-operation failures; correlated faults; and dependencies shared by apparent redundancy.
- Derive invariants for normal, degraded, recovering, and transitional states. Trace high-consequence scenarios end to end, including faults during mitigation or recovery. Inspect architecture-wide compositions first: individually reasonable timeouts, retries, queues, caches, replicas, autoscaling, and failover can create cascades, duplication, oscillation, or permanent divergence.
- Apply the baseline across every applicable component and boundary. Derive extra scenarios from the exact domain, topology, operating model, and history. Verify controls in representative conditions and in the exact call paths they protect.
Do not infer reliability from a framework default, managed service, retry/circuit-breaker helper, queue, transaction, replica, health check, autoscaler, naming convention, common pattern, test presence, or successful happy path. Verify exact versions, configuration, time budgets, state effects, ownership, deployment boundaries, correlated dependencies, and recovery behavior.
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 · 164 lines · 92 tokens per session scan A 47cb944981e5
audit-reliability is a skill published in the GitHub repository JHostalek/dotclaude (11 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 92 tokens to every session and 3,430 once invoked, about $0.0005 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
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
skill-check
Validate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.
agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
skill-template
Generate custom skill/command from template. Use when creating a new skill or slash command from scratch, or scaffolding a skill file with correct frontmatter.