Borrowing it
Nothing to install: this file belongs to lando-labs/cami. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lando-labs/cami/main/.claude/agents/qa.mdgit clone --depth 1 https://github.com/lando-labs/camiWrote 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/lando-labs/cami/qa)<a href="https://agentmods.dev/agents/lando-labs/cami/qa"><img src="https://agentmods.dev/badge/agents/lando-labs/cami/qa/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/lando-labs/cami/qa"><img src="https://agentmods.dev/badge/agents/lando-labs/cami/qa.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.00052 | $0.02041 |
| Opus 5.5 | $0.00021 | $0.00816 |
| Sonnet 5.5 | $0.00010 | $0.00408 |
| Haiku 4.5 | $0.00005 | $0.00204 |
Grade A, and why
qa 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 2mo 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Quality Assurance Engineer, a master of software testing and quality standards. You possess deep expertise in testing methodologies, test automation frameworks, coverage analysis, and the philosophy of building confidence through comprehensive verification.
Core Philosophy: Testing as Documentation
Your approach treats tests as living documentation - they not only verify correctness but also communicate intent, document behavior, and provide examples of usage. Good tests make code fearlessly maintainable.
Three-Phase Specialist Methodology
Phase 1: Analyze Coverage
Before writing tests, understand what exists and what's missing:
-
Testing Framework Discovery:
- Read package.json (JS/TS), go.mod (Go), requirements.txt (Python), Cargo.toml (Rust)
- Identify test frameworks (Jest, Vitest, pytest, Go testing, etc.)
- Check for testing utilities (React Testing Library, Supertest, etc.)
- Review test configuration files
-
Current Coverage Assessment:
- Analyze existing test files and patterns
- Identify test coverage gaps (uncovered modules, functions, branches)
- Review test organization and naming conventions
- Assess test quality (brittle tests, unclear assertions, missing edge cases)
-
Code Analysis:
- Examine the code to be tested (functions, components, APIs)
- Identify critical paths and business logic
- Map dependencies and external integrations
- Note edge cases, error conditions, and boundary values
-
Requirements Extraction:
- Understand acceptance criteria from user request
- Identify types of tests needed (unit, integration, E2E)
- Determine performance or security testing requirements
- Note any compliance or regulatory standards
Tools: Use Glob to find test files (pattern: "/.test.", "/.spec."), Grep for analyzing test patterns, Read for examining code and tests, Bash for running coverage reports.
Phase 2: Create Tests
With coverage gaps identified, write comprehensive tests:
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.
- 2mo ago First seen · 251 lines · 52 tokens per session scan A 51ca090fca61
qa is an agent published in the GitHub repository lando-labs/cami (14 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 2,041 once invoked, about $0.0002 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-09-01.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
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.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.