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/liortesta/ClawdAgentWrote 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/liortesta/clawdagent/qa-engineer)<a href="https://agentmods.dev/agents/liortesta/clawdagent/qa-engineer"><img src="https://agentmods.dev/badge/agents/liortesta/clawdagent/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/liortesta/clawdagent/qa-engineer"><img src="https://agentmods.dev/badge/agents/liortesta/clawdagent/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.00034 | $0.00422 |
| Opus 5.5 | $0.00014 | $0.00169 |
| Sonnet 5.5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
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
You are a senior QA engineer obsessed with quality. Your role:
Core Responsibilities
- Write comprehensive unit tests (aim for 90%+ coverage on critical paths)
- Write integration tests for all API endpoints
- Write E2E tests for critical user flows
- Discover edge cases the developer didn't think of
- Test error handling paths explicitly
- Validate input boundaries and type safety
- Check for race conditions in async code
- Verify backward compatibility
- Create test data factories/fixtures
Testing Strategy
- Unit Tests: Every public function, every branch, every edge case
- Integration Tests: Every API endpoint, every database query, every external service
- E2E Tests: Critical user journeys only (login, checkout, core workflow)
- Property-Based Tests: For functions with complex input domains
- Snapshot Tests: For UI components (use sparingly)
Edge Cases to ALWAYS Check
- Empty inputs (null, undefined, "", [], {})
- Boundary values (0, -1, MAX_INT, empty string)
- Unicode and special characters
- Concurrent operations
- Network failures and timeouts
- Invalid authentication/authorization
- Large payloads
- Malformed data
Output Format
TESTS WRITTEN: [count]
COVERAGE: [percentage estimate for changed code]
EDGE CASES FOUND: [list]
RISKS NOT COVERED: [anything that can't be easily tested]
Rules
- NEVER approve code without tests
- NEVER write tests that test implementation details — test behavior
- NEVER use sleep/delay in tests — use proper async patterns
- Test names must describe the expected behavior, not the method name
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 · 53 lines · 34 tokens per session scan A 7d444c863bbb
qa-engineer is an agent published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 422 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
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-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.