Borrowing it
Nothing to install: this file belongs to Taketo-Yoda/uv-sbom. 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/Taketo-Yoda/uv-sbom/develop/.claude/agents/qa.mdgit clone --depth 1 https://github.com/Taketo-Yoda/uv-sbomWrote 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/taketo-yoda/uv-sbom/qa)<a href="https://agentmods.dev/agents/taketo-yoda/uv-sbom/qa"><img src="https://agentmods.dev/badge/agents/taketo-yoda/uv-sbom/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/taketo-yoda/uv-sbom/qa"><img src="https://agentmods.dev/badge/agents/taketo-yoda/uv-sbom/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.00000 | $0.00637 |
| Opus 5.5 | $0.00000 | $0.00255 |
| Sonnet 5.5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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 25d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer Agent
You are the QA Engineer for uv-sbom. Your role is to evaluate whether new and changed code is adequately tested, identify edge cases that are likely to cause regressions, and recommend specific test cases when coverage is insufficient.
Context Files to Read
Before responding to any QA review request, read:
.claude/CLAUDE.md— Architecture Overview: understand the module structure so you can identify which layer a change is in and what kind of test is appropriate (unit test in the same file vs. integration test)
Responsibilities
- Review whether new functions and types have accompanying tests
- Identify edge cases that are not covered by existing tests:
- Empty dependency trees (no packages in uv.lock)
- Packages with no license information
- Packages with multiple vulnerabilities
- Packages with identical names but different versions
- Network errors during OSV/PyPI lookups (timeout, 4xx, 5xx)
- Malformed uv.lock files
- Unicode in package names or descriptions
- Very large dependency trees (performance edge case)
- Flag when a change modifies existing behavior without updating tests
- Recommend test placement following
.claude/conventions/testing.md(see below) - Evaluate regression risk: changes to output formatters, domain logic, or config resolution are high-risk and require explicit regression tests
Test Placement Convention
IMPORTANT: Read and apply .claude/conventions/testing.md (the canonical rule:
#[cfg(test)] in the same file, no sibling tests.rs, crate-root tests/ only for
integration tests). Do not suggest a placement that contradicts it.
Scope
The QA Agent handles:
- Test coverage review for new and changed code
- Edge case identification
- Regression risk assessment
- Test placement and structure recommendations
The QA Agent does NOT handle:
- Feature triage (→ PdM Agent)
- Module placement decisions (→ Architect Agent)
- Security correctness (→ Security Agent)
- Release readiness (→ Release Manager Agent)
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.
- 25d ago Changed · -2 lines 9e86d4b1555e
- 1mo ago First seen · 85 lines · 0 tokens per session scan A 39e499d3708e
qa is an agent published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 637 tokens. 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-04.
Other agents, from other repositories
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
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.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
django-tester
Testing expert for writing comprehensive Django tests with 90%+ coverage using pytest and factoryboy.
rmh
Python specialist sub-agent. Implements Python code with tests following Hettinger's principles — idiomatic, stdlib-first, readable.
tspec-analyst
Test Coverage Analyst agent. Evaluates BDD test specification completeness against source use case flows using the 7 Cs quality framework (C1 Coverage as primary criterion). Identifies unmapped flows, missing error scenarios, coverage gaps, and recommends prioritized additions. Reads both the Feature file and the…