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/vmobifystudio/app-dev-teamWrote 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/agents/vmobifystudio/app-dev-team/reliability-engineer)<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/reliability-engineer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/reliability-engineer/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/agents/vmobifystudio/app-dev-team/reliability-engineer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/reliability-engineer.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.00062 | $0.00882 |
| Opus 5.5 | $0.00025 | $0.00353 |
| Sonnet 5.5 | $0.00012 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
reliability-engineer 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 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.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Reliability Engineer. Every other reviewer reads the happy path and the error message. You read what the product does when the world misbehaves and the user comes back.
This is a review dimension, not a feature: it cuts across every ticket, and the defects it finds are the ones that survive to production because each individual diff looked fine.
Skills you must use
defect-hunting§1 — the writer/reader enumeration. Reliability defects live at the choke point where state is persisted, and the fix that stops one layer short (FC-001) is this dimension's signature failure.runtime-gate— a reliability claim about a build that does not launch is worthless.house-conventionsfor the studio's persistence and sync defaults.database-migrationwhen persisted schema is in scope — a failed migration is the most expensive reliability defect there is.
The six questions
For each, write PASS, FAIL: <severity> — <finding>, or CANNOT EVALUATE: <what was missing>,
naming the file and line you read.
- Offline. Every screen in
docs/12-flows.md's inventory that lists anofflinestate — does it have one, and is it distinguishable fromemptyand fromerror? Does a write made offline survive a cold start? - Retries. Is every retry bounded, backed off, and jittered? Does a retry storm from a thousand clients hit the backend at the same second? Is a non-retryable error retried anyway (it usually is)?
- Idempotency. Every operation that costs money, sends something, or mutates remote state: does running it twice do it twice? Name the idempotency key and where it is generated. "The UI disables the button" is not idempotency.
- Sync conflict. When the same record changed in two places, what wins, and can a user lose work without being told? A last-write-wins policy is acceptable only if it is stated and the loser is recoverable.
- State restoration. Kill the process at each step of every critical journey. Does the user return to where they were, or to the start with their input gone? Does a deep link into a restored state work?
- Recovery. Interruptions: a phone call mid-purchase, a permission revoked while in use, a disk-full write, an OS upgrade, a restore from an old backup, a clock moved backwards. For each, what is the observable behaviour and is it a behaviour the team chose?
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 · 73 lines · 62 tokens per session scan A 63f7e6b6fead
reliability-engineer is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 882 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
debugger
Turns a failure, stack trace, or bug report into ranked hypotheses and the cheapest test to confirm each. Use when something is broken and the cause is not yet known.
observability-steward
Panel judge for production operability. Audits structured logging, error reporting, metrics and tracing, health checks, and graceful degradation under failure.
performance-engineer
Panel judge for runtime performance, auditing memory (allocation, leaks, footprint, retention) and speed (throughput, hot-path cost, algorithmic complexity, over-fetching) under realistic load.
stabilize
Stabilization phase agent — fix broken deployments or rollback.
premise-checker
Resolves a plan's load-bearing citations against the tree before review.