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 Everyone-Needs-A-Copilot/claude-copilot --skill qagit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/qa)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/qa"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/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/skills/everyone-needs-a-copilot/claude-copilot/qa"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.02375 |
| Opus 5.5 | $0.00018 | $0.00950 |
| Sonnet 5.5 | $0.00009 | $0.00475 |
| Haiku 4.5 | $0.00004 | $0.00237 |
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 6d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
Use this skill to make quality concrete.
Operating Lens
- Verify behavior, not just builds.
- Reproduce defects before fixing when possible.
- Cover edge cases: empty, null, invalid, boundary, permission, race, and recovery paths.
- For product-facing work, verify design intent, workflow quality, visual fidelity, responsive behavior, accessibility, and product language.
- Check alignment with
SOUL.md, architecture guiding principles, or specialist design outputs when they apply. - Prefer deterministic tests that explain the expected behavior.
- Report residual risk honestly.
- Use Live Docs when verifying behavior tied to installed third-party APIs.
- Verify the fixed acceptance scope with Proportional Verification.
Success Criteria
- Acceptance criteria are explicit.
- Relevant tests or checks are run and reported.
- Edge cases and regression paths are covered in proportion to risk.
- Product-facing changes include design-fidelity checks.
- QA verdict is recorded in a
testwork product when task context exists. - Passing QA verdicts cite an external
ARTIFACT:marker, not only the model's judgment. - QA-required tasks can pass
scripts/copilot-gate.sh.
Workflow
- Check task and implementation work products when a task exists.
- Hydrate config and search memory for prior failures when
ccis configured. - Define the behavior under test and acceptance criteria.
- Use
cc docs get <pkg>when verification depends on installed third-party APIs. - Identify likely regression paths, edge cases, and design-fidelity risks.
- Run or write the smallest meaningful tests.
- Exercise user-facing flows when UI or workflow behavior changed.
- Inspect responsive states, accessibility behavior, visual hierarchy, and product language when product-facing.
- Store a
testwork product with anARTIFACT:marker andVERDICT: APPROVED,VERDICT: APPROVED-WITH-MINOR-FIXES, orVERDICT: REJECTED.
Output
Return:
- acceptance criteria
- tests/checks run
- design-fidelity checks when product-facing
- pass/fail verdict
- uncovered risk
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.
- 6d ago Changed e177b8a6e02c
- 7d ago Changed · +18 lines dfb9fdaf0395
- 1mo ago Changed · +4 lines d0588934337e
- 1mo ago Changed · +71 lines 97a2082977d1
- 1mo ago Changed · +3 lines 7b1c06a1e276
- 1mo ago First seen · 93 lines · 44 tokens per session scan A 20d0789dbae7
qa is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 2,375 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-04.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
module-regression
Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed module and every affected downstream command, and use observed exit codes as regression evidence under the project's…
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-flakiness
Find flaky tests from CI logs — aggregates pass rates, spots intermittent failures, recommends quarantine. After multiple runs.
maintain-formal-verification-skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for…
prevent-recurrence
Use when correcting an issue or failure reveals a reusable prevention lesson, including code, setup, measurement, validation, workflow, agent mistakes, or accepted code-review findings; when someone says "this keeps happening" or asks how to stop it; or in post-incident follow-up. Fixes the instance (failing-first…