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.
npx skills add krzysztofsurdy/code-virtuoso --skill qa-engineergit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/skills/krzysztofsurdy/code-virtuoso/qa-engineer)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/qa-engineer"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/qa-engineer.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.00070 | $0.02155 |
| Opus 5 | $0.00035 | $0.01077 |
| Sonnet 5 | $0.00014 | $0.00431 |
| Haiku 4.5 | $0.00007 | $0.00215 |
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 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
Own the quality gate for a feature or release. Translate requirements and acceptance criteria into structured test plans, execute tests, report defects, and sign off when the build is ready to ship.
Role Summary
- Responsibility: Plan testing, write test cases, execute tests, report bugs, verify fixes, sign off on releases
- Authority: Block releases when critical bugs are open, classify bug severity, define test coverage requirements
- Escalates to: Product Manager when acceptance criteria are ambiguous or incomplete
- Deliverables: Test plans, test cases, bug reports, test summaries, release sign-off
When to Use
- A new feature has acceptance criteria ready and needs a test plan
- A build or release candidate needs structured verification before deployment
- Bug reports need to be written with clear reproduction steps and severity classification
- Test coverage gaps need to be identified and addressed
- A release decision is pending and someone must assess overall quality
- Exploratory testing is needed to find issues that scripted tests miss
Workflow
Phase 1: Plan
Input: PRD with acceptance criteria, architecture docs, system context
- Review all acceptance criteria and non-functional requirements from the PRD
- Identify the scope of testing — what is being tested and what is explicitly excluded
- Determine the test types required (functional, integration, regression, performance, security)
- Define entry criteria — what must be true before testing begins
- Define exit criteria — what must be true before testing is considered complete
- Identify test environment and test data requirements
- Assess risks and define mitigations (e.g., unstable dependencies, missing test data)
- Produce the test plan following references/test-plan-template.md
Output: Test plan document covering scope, approach, environments, schedule, entry/exit criteria, and risks
Phase 2: Design
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 195 lines · 70 tokens per session scan A 4449e0684fe8
qa-engineer is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (20 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 2,155 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-30.
Other skills, from other repositories
instruction-eval
Change one condition an agent runs under (instruction text, the reference material instructions point at, MCP tools and permissions, hooks, skill files), then run the same prompts before and after, several times each, to see what actually changes. Produces an HTML report showing both arms' answers side by side. Use…
create-qa-list
Turn code, specs, a PR, or the current conversation into a QA test-case list a non-developer can read and run, exported as CSV, a shareable HTML report, or both. Trigger when the user wants QA test cases, a test plan, a QA checklist, or a test-case CSV/HTML (e.g. "write test cases for this", "make a QA list"). Output…
openclaw-test-heap-leaks
Investigate pnpm test memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the scripts/test-parallel.mjs heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated .heapsnapshot files, compare snapshots from the same worker PID, distinguish…
openclaw-parallels-smoke
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip…
cargo-test
Skill "cargo-test" from rootwarp/claude-code-plugins-monorepo, covering /cargo-test and instructions.
go-test
Skill "go-test" from rootwarp/claude-code-plugins-monorepo, covering /go-test and instructions.