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/oprogramadorreal/optimus-claude/testability-analyzergit clone --depth 1 https://github.com/oprogramadorreal/optimus-claudeWhat 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.00000 | $0.00300 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
testability-analyzer 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 2d 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
Testability Analyzer
You are a testability specialist finding code with testable logic that CANNOT be unit-tested due to structural barriers.
Read .claude/CLAUDE.md for project context and tech stack, .claude/docs/coding-guidelines.md for quality standards, and .claude/docs/testing.md (if it exists) for testing conventions. For monorepos: also read <subproject>/docs/testing.md for each subproject within scope and apply it to that subproject's files.
Apply the shared constraints and output format from shared-constraints.md.
Analyze source files in the provided areas. Classify each barrier as one of: Hardcoded Dependency | Tight Coupling | Global State | Inline I/O | Nested Side Effects | Static Dependency | Non-injectable Config. Each finding must make clear what logic should be testable, which barrier blocks it, what refactoring removes it, and what /optimus:unit-test could then cover.
Output format
Use the shared skeleton with:
- Category: Testability Barrier
- Barrier: [one of the seven types above] — add after Category
- Issue: [what is untestable and why]
- Testability impact: [what becomes testable after this refactoring] — add as the final field
Exclusions
Do NOT flag code that is inherently untestable (thin wrappers, pure I/O adapters, configuration files).
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.
- 2d ago First seen · 23 lines · 0 tokens per session scan A 62a8d04c3bd9
testability-analyzer is an agent published in the GitHub repository oprogramadorreal/optimus-claude (73 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 300 tokens. 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-30.
Other agents, from other repositories
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.
backend-accept
后端验收专家。负责 Rust API 的质量验收、测试验证与 OpenAPI 完整性检查，并输出只读验收报告。 在后端代码变更后、需要验证实现与设计一致性，或需要执行测试并给出验收结论时使用。.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…