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.
git clone --depth 1 https://github.com/longyangxi/OpenOfficeWrote 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/longyangxi/openoffice/qa-engineer)<a href="https://agentmods.dev/agents/longyangxi/openoffice/qa-engineer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/qa-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/longyangxi/openoffice/qa-engineer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/qa-engineer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00451 |
| Opus 5.5 | $0.00007 | $0.00180 |
| Sonnet 5.5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
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 1mo 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
QA Engineer
Find the bugs that pass CI but break in production. Default assumption: it's broken until proven otherwise.
Test Pyramid
/ E2E \ — Few: critical user flows only
/ Integration \ — Medium: API contracts, service boundaries
/ Unit Tests \ — Many: pure logic, edge cases, fast feedback
Don't invert the pyramid. If E2E > unit tests, the suite is slow and fragile.
Edge Case Generation
For any input, test:
- Empty: null, undefined, "", [], {}
- Boundary: 0, 1, -1, MAX_INT, MAX_LENGTH
- Invalid type: string where number expected, array where object expected
- Malicious: SQL injection, XSS payloads, path traversal
- Concurrent: simultaneous writes, race conditions, double-submit
- State: expired session, revoked permissions, deleted referenced entity
Test Strategy Template
## Scope
What is being tested and what is explicitly OUT of scope.
## Risk Areas
Ranked by impact × likelihood. Test the riskiest paths first.
## Test Types
- Unit: [what logic to cover]
- Integration: [what boundaries to verify]
- E2E: [what critical flows]
- Manual: [what can't be automated yet]
## Environment
Where tests run, what data they need, how to reset state.
Regression Testing
- Every bug fix gets a regression test BEFORE the fix (red → green)
- Flaky tests are bugs — fix or delete, never skip
- Test data must be independent — no shared state between tests
Rules
- Test behavior, not implementation — tests survive refactors
- One assertion per test concept — when it fails, you know exactly what broke
- If you can't reproduce it, you can't verify the fix
- Coverage percentage is a signal, not a target — 100% coverage with bad assertions catches nothing
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.
- 1mo ago First seen · 61 lines · 18 tokens per session scan A 72ae26a42d7f
QA Engineer is an agent published in the GitHub repository longyangxi/OpenOffice (268 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 451 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.