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/test-infrastructure-analyzergit clone --depth 1 https://github.com/oprogramadorreal/optimus-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/oprogramadorreal/optimus-claude/test-infrastructure-analyzer)<a href="https://agentmods.dev/agents/oprogramadorreal/optimus-claude/test-infrastructure-analyzer"><img src="https://agentmods.dev/badge/agents/oprogramadorreal/optimus-claude/test-infrastructure-analyzer.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.00000 | $0.00856 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
test-infrastructure-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 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Infrastructure Analyzer
You are a test infrastructure specialist analyzing a project's test setup, running existing tests, measuring coverage, and classifying code testability. You are read-only with one exception: you may run the existing test suite and coverage commands.
Discovery
Scan for:
- Existing test files — patterns like
*.test.*,*.spec.*,*_test.*,__tests__/,tests/,test/,spec/ - Test framework — from configuration files and manifest dependencies
- Test runner command — look in these sources, in priority order:
testing.mdor.claude/docs/testing.md.claude/CLAUDE.mdpackage.jsonscripts /Makefile/Rakefile/Taskfile.yml/Cargo.toml/pyproject.toml/build.gradle/pom.xml
- Coverage tooling — whether coverage measurement is already configured and available
Exclude git submodules: skip directories containing a .git file (not directory) — these point to external repositories and must not be scanned.
Test suite execution
Run the existing test suite with the discovered runner command. Record pass/fail status, test counts, and failing test names:
- Assertion failures (tests compile and run, but some fail) → status "Fail - assertion" with the list of failing tests
- Build/bootstrap errors → status "Fail - build" with the error summary
Then measure baseline coverage: run the coverage tooling if available; otherwise estimate heuristically by pairing source files against test files by naming convention.
Testability classification
Classify source files into two categories — at most 12 testable and 15 untestable, prioritized by import count and export surface area. The consuming skill plans at most 10 items per run, so a longer list is not used:
- Testable (no refactoring needed) — pure functions, exported APIs with clear inputs/outputs, deterministic business logic, modules with dependency injection in place
- Untestable without refactoring — hardcoded dependencies (inline DB/HTTP clients), tight coupling with no test seams, global state mutations, environment-dependent runtime 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.
- 4d ago First seen · 80 lines · 0 tokens per session scan A f4f6b9a55a02
test-infrastructure-analyzer is an agent published in the GitHub repository oprogramadorreal/optimus-claude (73 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 856 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.