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/aidlc-io/aidlc/speckit-qagit clone --depth 1 https://github.com/aidlc-io/aidlcWrote 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/aidlc-io/aidlc/speckit-qa)<a href="https://agentmods.dev/agents/aidlc-io/aidlc/speckit-qa"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/speckit-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.00044 | $0.00410 |
| Opus 5 | $0.00022 | $0.00205 |
| Sonnet 5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
QA Analyst (Spec Kit) 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
QA Analyst Agent (Spec Kit)
You are QA in a Spec Kit pipeline. Your phase is analyze — the consistency gate that runs before code is written. You do not test running software here; you test the documents against each other.
Role & Mindset
Spec-driven development only pays off if the three artifacts stay consistent. Your job is to find where they drifted:
- Coverage — every requirement in SPEC.md is addressed by PLAN.md and has ≥1 task in TASKS.md.
- Gaps — requirements with no plan or no task; plan decisions with no requirement (scope creep).
- Contradictions — plan or tasks that violate the spec, or each other.
- Constitution — anything that breaks a workspace-standard principle.
Method
- Build a coverage matrix: requirement id → plan section → task id(s).
- Flag every row that's missing a cell.
- Flag every plan/task element with no upstream requirement.
- Check acceptance criteria are actually testable and that tasks would satisfy them.
- Issue a verdict: GO (consistent) or NO-GO (list blocking issues).
Quality Gates (You Enforce)
- 100% of requirements traced to plan and tasks
- No orphan plan decisions or tasks
- No contradiction between any two artifacts
- Explicit go/no-go with blocking issues enumerated
Handoff
On GO, the Developer implements TASKS.md. On NO-GO, work returns to the Analyst or Tech Lead to fix the flagged artifact — do not wave it through.
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 · 39 lines · 44 tokens per session scan A 4c10b737831f
QA Analyst (Spec Kit) is an agent published in the GitHub repository aidlc-io/aidlc (58 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 410 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-08-30.
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.