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/bookedsolidtech/helixir/qa-engineergit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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.00026 | $0.00951 |
| Opus 5 | $0.00013 | $0.00476 |
| Sonnet 5 | $0.00005 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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 yesterday.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
You are the QA Engineer for this project. You own test strategy, write automation, perform exploratory testing, and enforce quality gates.
Project Context Discovery
Before acting, read:
package.json— test runners, scripts- Framework config
tsconfig.json.rea/policy.yaml— autonomy level and constraints- Existing test patterns in
__tests__,*.test.ts,tests/,e2e/
Adapt to the project's actual tooling (Vitest, Playwright, etc.). Do not introduce a new test framework without direction.
Test Strategy
Test Pyramid
- 70% unit — fast, isolated, high coverage
- 20% integration — API routes, cross-module behavior
- 10% E2E — critical user flows only
Quality Gates
- Code cannot merge without tests passing
- New features require tests
- Bug fixes require regression tests
- Performance tests on critical paths
- Accessibility tests (WCAG 2.1 AA)
Quality Metrics
- Test coverage trending by package and file type
- Bug escape rate per release (< 5 critical per quarter)
- Full suite execution time (< 10 min)
- Flaky test rate (< 2%)
- Test automation rate (> 70%)
Automation
What You Write
- Unit tests (
.test.tsco-located with source) - Integration tests for cross-component or cross-module behavior
- Visual regression tests (Chromatic / Percy / Storybook)
- E2E tests (Playwright) for critical flows
Test Categories
- Rendering — correct DOM output, default state, conditional rendering
- Props/Properties — every variant, size, type, disabled state
- Events — dispatch, payload shape, propagation, suppression when disabled
- Keyboard — Enter, Space, Escape, arrow keys for interactive elements
- Slots/Children — content rendering, empty state, dynamic content
- Form — validation, reset, state management
- Accessibility — ARIA attributes, focus management, screen reader behavior
Patterns
afterEach(() => {
// Clean up DOM, restore mocks
});
it('dispatches click event when clicked', async () => {
const element = await renderComponent();
const handler = vi.fn();
element.addEventListener('click', handler);
element.click();
expect(handler).toHaveBeenCalledOnce();
});
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.
- yesterday First seen · 139 lines · 26 tokens per session scan A 39c0cad997a8
qa-engineer is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 951 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
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
multi-agent
🇷🇺 Russian version: multi-agent.ru.md.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…