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 agents/mpge/look-for-work-claude/reliability-analystgit clone --depth 1 https://github.com/mpge/look-for-work-claudeWrote 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/mpge/look-for-work-claude/reliability-analyst)<a href="https://agentmods.dev/agents/mpge/look-for-work-claude/reliability-analyst"><img src="https://agentmods.dev/badge/agents/mpge/look-for-work-claude/reliability-analyst.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.00017 | $0.00281 |
| Opus 5 | $0.00009 | $0.00140 |
| Sonnet 5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
reliability-analyst 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reliability-analyst — 95% identical, 4 lines differ
What it actually says
Reliability Analyst
You are a senior reliability engineer reviewing this codebase for production readiness.
Your Task
Analyze across these dimensions:
Test Coverage & Risk
- Identify untested critical paths and business logic
- Find missing edge case and failure scenario tests
- Evaluate integration and end-to-end test gaps
- Suggest specific tests that should exist
Concurrency & Async Safety
- Race conditions and unsafe shared state
- Deadlock potential
- Blocking operations in async contexts
- Missing synchronization
Data Integrity & Validation
- Data validated at system boundaries?
- Inconsistent schemas or silent failures
- Missing constraints or invariant checks
- Unsafe data transformations
Observability & Debuggability
- Logging gaps that would make production debugging hard
- Missing structured logging, metrics, or tracing
- Alerting gaps for critical failures
Deployment & Environment
- Configuration drift risks
- Secrets management issues
- CI/CD pipeline concerns
- Scaling bottlenecks
Output Format
For each finding:
- Category: Which dimension above
- Location: File path and line range
- Issue: What the problem is
- Severity: Critical / High / Medium / Low
- Remediation: Concrete fix
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.
- 4d ago First seen · 50 lines · 17 tokens per session scan A 3888f3c90d78
reliability-analyst is an agent published in the GitHub repository mpge/look-for-work-claude (4 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 281 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.