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/dhaupin/vant/vant-skill-audit-reliabilitynpx skills add dhaupin/vant --skill vant-skill-audit-reliabilitygit clone --depth 1 https://github.com/dhaupin/vantWrote 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/dhaupin/vant/vant-skill-audit-reliability)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-audit-reliability"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-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.1 | $0.00009 | $0.00487 |
| Opus 5 | $0.00005 | $0.00244 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
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 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.
What it actually says
Reliability
Can it recover?
The Question
When it breaks, does it come back?
What To Check
1. Graceful Degradation
// What happens when X fails?
try {
doX()
} catch {
// Does it fail safe?
return default
}
| Check | Issue | Fix |
|---|---|---|
| No fallback | Everything dies | Add default |
| No retry | One fail = fail | Retry |
| No circuit | Cascade fail | Circuit break |
2. Recovery
// Can it restart?
process.on('uncaught', () => {
// Log and restart?
})
| Check | Issue | Fix |
|---|---|---|
| No restart | Stay down | Auto-restart |
| No logging | Can't debug | Log it |
| No alerts | Can't know | Alert |
3. Data
// What if DB fails?
await db.save(x)
// vs
await db.save(x)
.catch(log)
| Check | Issue | Fix |
|---|---|---|
| No backup | Lost forever | Back up |
| No transactions | Partial | Use transaction |
| No validation | Bad data | Validate |
4. Capacity
| Check | Limit |
|---|---|
| Auto-scale | Yes/No |
| Max instances | [n] |
| Queue depth | [n] |
Output
## Reliability - [system]
### Failure Mode
- [SAFE/FAIL] If [X] fails: [behavior]
### Recovery
- [YES/NO] Auto-restart
- [YES/NO] Alert on fail
- [YES/NO] Log on fail
### Data
- [YES/NO] Backup
- [YES/NO] Transactions
### Capacity
- [n] max
- Auto-scale: [YES/NO]
### MTTR (mean time to recover)
- Target: [m]min
Role: Reliability Auditor
Input: System
Output: Can recover?
Plan for failure.
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.
- 6d ago First seen · 115 lines · 9 tokens per session scan A d6451e7e3b7a
audit-reliability is a skill published in the GitHub repository dhaupin/vant (9 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 487 once invoked, about $0.0000 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
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…
doctor
Explicit Codex workflow: Run strictly read-only Codex plugin, MCP contract, schema, and environment diagnostics; recommend but never execute recovery.
debug-screen
Explicit Codex workflow: Diagnose why the current screen is broken, showing unexpected content, or crashing. Gathers parallel evidence from all layers and applies a targeted fix.
performance-optimization
Measure-first performance work. Use on triggers like "it's slow", "profile this", "optimize perf", "fix the bottleneck", "improve load time / Core Web Vitals", or when a measured regression needs fixing. Enforces measure-before-optimize. Fills a perf gap not covered by existing project skills. Not a build/ship…
ci-troubleshoot
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 10-file workflow taxonomy, the release pipeline, known failure modes, and how to read gh run logs and retrigger jobs. Use when a CI run is red, a release is stuck, a workflow won't dispatch, or you need to know which workflow does what. See release-cut to…