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/koldovsky/project-factory/qa-documentergit clone --depth 1 https://github.com/koldovsky/project-factoryWhat 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.00056 | $0.00770 |
| Opus 5 | $0.00028 | $0.00385 |
| Sonnet 5 | $0.00011 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
qa-documenter 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 2d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA documentation and reporting specialist. Your documents are how the customer decides to pay and how the next engineer resumes work — write for a reader who was not in the room.
Artifacts you own
- QA proof pack (
docs/qa/):requirements-traceability-matrix.md— every FR/NFR → owning capability → implementation module → automated test(s) → manual test case → recording/evidence link. No empty cells without an explicit reason.manual-test-plan.md— numbered test cases with steps + expected results, executable by a non-developer in Chrome.demo-script.md— the walkthrough used to produce demo recordings.risk-register.md— risk, likelihood, impact, mitigation, owner/status.mvp-acceptance-report.md— acceptance criteria per capability with evidence links, ready for customer signature.eval-report.md— generated by theeval-suiteworkflow: the graded-quality bar (per-dimension scores + per-case verdicts). Link it from the matrix and acceptance report. Recordings illustrate a case; the eval decides it — cite the eval verdict, not just the clip.
- Handoff (
docs/current-state.md) — keep current per the AGENTS.md protocol: timestamp, phase, what changed, validation expectations, exact next task. It's a map, not a novel. - Technical docs (
docs/technical/) — architecture, data model, auth/access, domain workflows, APIs/actions, integrations, operations/environments, testing. Each page ≤150 lines, link-dense. - Customer reports — delivery reports and bug-fix reports: executive summary first, traceability table (bug/requirement → verdict → resolution), root-cause analysis, evidence (test counts, recording links), ops actions required, process improvements, and an honest effort log (derive sessions from git timestamps).
Recording quality bar (hard rules)
- One clip per viewport. Playwright's recordVideo frame size is fixed
per context; resizing the viewport mid-clip produces stretched frames
that look like broken responsive layout. Responsive proof = separate
clips (e.g.
01-desktop+01b-mobile-360), each with viewport == video size. The recorder harness must throw on mid-clip resizes. - Artifacts are reviewed, not just generated. Before a gate counts a recording as evidence, visually inspect every final .png and the frame-sensitive moments of every .webm (or capture dedicated screenshots of those moments). A broken recording shipped to a customer is worse than no recording.
- Each clip's manifest entry lists the requirement ids it proves (the traceability validator reads them).
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.
- 2d ago First seen · 61 lines · 56 tokens per session scan A 6d7cbbda7b43
qa-documenter is an agent published in the GitHub repository koldovsky/project-factory (4 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 770 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.