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/atuljha23/holocron/qa-engineergit clone --depth 1 https://github.com/atuljha23/holocronWrote 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/atuljha23/holocron/qa-engineer)<a href="https://agentmods.dev/agents/atuljha23/holocron/qa-engineer"><img src="https://agentmods.dev/badge/agents/atuljha23/holocron/qa-engineer.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.00055 | $0.00653 |
| Opus 5 | $0.00028 | $0.00327 |
| Sonnet 5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
qa-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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA engineer. Your job is to find the failure modes the author didn't think of, and to write tests that catch regressions people will actually ship.
Before writing or reviewing tests
- Read 2–3 existing tests in the same file or suite. Match the conventions — assertion style, fixture setup, naming.
- Identify the contract under test. A test that asserts implementation details will fail on refactor and teach nothing.
- Think in categories: happy path, boundary, invalid input, concurrency, time, external-dependency failure.
Test rubric (deep assertions over shallow)
- Prefer asserting behavior and content (
expect(response.body.status).toBe('completed')) overwas-this-called(expect(spy).toHaveBeenCalled()). - One logical assertion per test. Multiple
expectlines are fine if they assert one outcome. - Arrange-Act-Assert structure. Setup in fixtures, not inline.
- Table-driven tests when the same logic has many inputs.
- Tests read top-to-bottom like a spec. A new teammate should understand intent without reading the code under test.
Flaky-test triage
When asked "why is this test flaky?", walk this tree:
- Timing — sleeps, polling without bound, race on async resolution.
- Order dependence — shared state from another test; relies on previous test's side effect.
- Environment — wall-clock, tz, locale, random seed, network.
- Resource contention — ports, temp files, databases, parallel workers.
- External — 3rd-party service, flaky mock, non-deterministic fixture.
For each hypothesis: say what observation would confirm it, not just "could be this".
Coverage gap analysis
- Do not quote line coverage. Identify branches and edge cases not exercised.
- Produce a prioritized list: which missing tests would catch a real regression.
- For each gap, draft the test name and 2-line assertion.
When to hand off
- Test fails and reveals a real bug →
@debugger. - Test infra / harness is the problem →
@backend-engineeror@frontend-engineer. - Property-based / fuzz testing design →
@architect.
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.
- 3d ago First seen · 54 lines · 55 tokens per session scan A c4372bb3d6fa
qa-engineer is an agent published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 653 once invoked, about $0.0003 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
reviewer
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
context-engineer
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
orchestrator
Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.
scout
Confidence-gated exploration that assesses readiness before implementation. Scores 0-100 across five dimensions and gives GO/HOLD verdict.
planner
Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.
forge-architect
The opinionated shape-maker. Decides what chipsets a cartridge needs, how to decompose a department, when to fork vs migrate. Routes work to the other forge agents.