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 agentmods add skills/drvoss/everything-copilot-cli/qa-reviewnpx skills add drvoss/everything-copilot-cli --skill qa-reviewgit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/qa-review)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/qa-review"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/qa-review.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 | $0.00043 | $0.01447 |
| Opus 5 | $0.00022 | $0.00724 |
| Sonnet 5 | $0.00009 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
qa-review 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 today.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Review
Review quality strategy the way a strong QA engineer would: choose the right test layers, verify the tests are readable and deterministic, and make failures easy to act on.
When to Use
- A feature or PR needs a QA-oriented review before merge or release
- Test coverage exists, but you are not sure it is at the right pyramid level
- A team needs a repeatable checklist for API, UI, regression, or performance coverage
- Bug reports or CI failures are noisy and need better quality standards
When NOT to Use
| Instead of qa-review | Use |
|---|---|
| Writing one failing test before implementation | tdd-workflow |
| Building an LLM or agent evaluation suite | eval-harness |
| Writing or debugging browser automation for a specific flow | e2e-testing or browser-devtools |
| General UX or usability critique | ux-audit |
QA Model
Balance the test pyramid first:
| Layer | Goal | Typical share |
|---|---|---|
| Unit | business logic, edge cases, fast feedback | 60-70% |
| Integration | module boundaries, DB, API, contracts | 20-30% |
| End-to-end | critical user journeys and smoke flows | 5-10% |
If a change leans too heavily on slow end-to-end tests or skips contract-level checks entirely, treat that as a QA design issue, not just a missing test.
Workflow
1. Define the quality risk
Before reading tests, ask:
- what can break for the user or operator?
- which layer should catch it first?
- what would make a failure actionable in CI?
Use that to decide whether you primarily need unit, integration, E2E, or performance evidence.
2. Inspect the current test surface
rg -n "describe\\(|test\\(|it\\(" . -g "*.{test,spec}.{js,jsx,ts,tsx}"
rg -n "def test_|class Test" . -g "*_test.py" -g "test_*.py"
rg -n "@playwright/test|cypress|selenium" .
Check whether the tests already map to the right layer or whether important paths are covered only indirectly.
3. Review test case quality
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.
- today First seen · 199 lines · 43 tokens per session scan A 73f6ddbf1fff
qa-review is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 1,447 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-dev-workflow
Build and run workflow for WinUI 3 apps with WinApp CLI 0.6+ — project creation with winapp new, project-mode winapp run, BuildAndRun.ps1 analyzer integration, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.
winui-packaging
MSIX packaging, code signing, and distribution for WinUI 3 apps — build for release, certificate generation (winapp cert generate), certificate trust, code signing (winapp sign), self-contained deployment, CI/CD with GitHub Actions, and Microsoft Store submission. Use when preparing for release, creating MSIX…
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
journey-template
Create new agentic journeys from app ideas. Generates README.md (learner walkthrough), PLAN.md (AI-readable spec), and app-specific skills for OSS deployments. Supports any stack (Node.js, Python, .NET, Java, Swift, Kotlin) and Azure service (Container Apps, AKS, Functions, App Service). USE FOR: new journey, scaffold…