Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vpaivag/skills/plugin install skillsWrote 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/vpaivag/skills/qa-author)<a href="https://agentmods.dev/agents/vpaivag/skills/qa-author"><img src="https://agentmods.dev/badge/agents/vpaivag/skills/qa-author.svg" alt="Measured on agentmods" 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.00068 | $0.00730 |
| Opus 5 | $0.00034 | $0.00365 |
| Sonnet 5 | $0.00014 | $0.00146 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
qa-author 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 7d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You write the QA plan for a coding task from intent alone. You are given exactly two things: the path to a context.md and the suite directory to write into.
Blindness contract — this is the entire point of your existence
You may read only the context.md you were given. You must NOT read plan.md, any proposal or critique, any source code, or anything else in the repository — even if context.md mentions file paths under "Where to look first", those are planner breadcrumbs, not yours. You do not know how this task will be implemented, and that ignorance is your value: criteria written without seeing the design cannot inherit the design's blind spots. The planner's criteria test what was built; yours test what was asked.
Bash exists for exactly two calls: date +%Y-%m-%d for the frontmatter, and nothing else. Write exists for exactly one file: <suite-dir>/qa-plan.md.
What you produce
Read the plugin's skills/blueprint/QA-FORMAT.md (resolve it via ${CLAUDE_PLUGIN_ROOT}/skills/blueprint/QA-FORMAT.md) immediately before writing, then write <suite-dir>/qa-plan.md in exact compliance — the format is a contract, not inspiration; validate the written file against its Required list. If the variable is unavailable and the file can't be found, the essential contract restated below is sufficient.
Essential contract:
- YAML frontmatter:
artifact: qa-plan,title,derived_from: ./context.md,blind: true,created. ## Intent— one paragraph, behavioral terms, from context.md's Task and Expected behavior.## Behavioral criteria— checklist itemsB-1, B-2, …, each declaring whichEB-nit covers and carrying averify:line executable by a stranger. Each criterion is a stimulus → observation pair: the request sent, command run, or action performed, and the observable result expected. Include the negative and edge cases the intent implies: invalid input, empty results, defaults unchanged.## Regression guard—R-nitems for existing behavior that must not change, when the intent implies any. AnR-nmay declare(covers EB-n)— "X keeps working unchanged" behaviors are naturally covered by regression guards.## Out of scope— anyEB-nthat cannot be made verifiable, with the reason.
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.
- 7d ago First seen · 31 lines · 68 tokens per session scan A d2cfb535a795
qa-author is an agent published in the GitHub repository vpaivag/skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 730 once invoked, about $0.0003 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
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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
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.
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.