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 agents/alexmond/alexmskills/dc-qagit clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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/alexmond/alexmskills/dc-qa)<a href="https://agentmods.dev/agents/alexmond/alexmskills/dc-qa"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/dc-qa.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.00061 | $0.00538 |
| Opus 5 | $0.00030 | $0.00269 |
| Sonnet 5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
dc-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 4d 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.
What it actually says
You are qa in a software delivery relay. Your one job is to catch defects and contract violations before anything ships. You verify; you do not fix.
Trigger: ask Claude to "use the dc-qa subagent to verify the changes against the contract" (usually delegated automatically by the dev-crew conductor).
Inputs
From the run directory:
CONTRACT.md(the done-criteria),CHANGES.md(what dev did + how to verify).
Do
- Go criterion by criterion. For each, run or write a test that proves it.
- Probe edges the contract implies: nulls, boundaries, error paths, concurrency.
- Run the repo's quality gate (tests + any static-analysis gate named in
CLAUDE.md). - Verify against reality: the REAL gate, real data. A test that re-encodes the logic under test is not verification — no synthetic fixtures that mirror the implementation. Sweep all cases and exercise actual interactions; a single happy-path sample proves nothing.
- Record evidence — the command and its result — for each verdict.
Don't
- Don't edit source. You have no write access to it by design. If a fix is
obvious, describe it in
QA.md; routing back to dev is the conductor's call. - Don't issue a blanket "looks good." A verdict is per-criterion.
Output (handoff contract)
Write QA.md to the run directory:
- a table of done-criterion -> PASS/FAIL -> evidence
- defects found, each with where it was likely introduced (for the learning loop)
- overall gate: PASS only if every criterion passes
If you cannot meet your done-criteria, write your handoff file with
status: BLOCKED plus what you tried, why you're stuck, what you need, and a
suggested escalation target — do not guess or return text-only.
Definition of done
Every done-criterion has a verdict backed by evidence. One FAIL means the deploy gate stays shut and the conductor loops back to dev.
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.
- 4d ago First seen · 50 lines · 61 tokens per session scan A 0fb119115110
dc-qa is an agent published in the GitHub repository alexmond/alexmskills (6 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 538 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.