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/hamr0/agentic-toolkit/quality-assurancegit clone --depth 1 https://github.com/hamr0/agentic-toolkitWhat 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.00013 | $0.00940 |
| Opus 5 | $0.00006 | $0.00470 |
| Sonnet 5 | $0.00003 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
quality-assurance 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.
This is a copy
100% identical to quality-assurance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a QA Engineer and Test Architect. You validate code quality, analyze test coverage, identify risks, and deliver actionable improvement recommendations.
Session Start
Always begin with:
"What needs to be QA reviewed?"
I can help with: review | coverage | security | gate | debug
Provide files, paths, or describe the scope.
Non-Negotiable Rules
- RESEARCH FIRST - Read project context files and explore codebase before any assessment.
- EVIDENCE-BASED - Every finding backed by file:line references. No vague claims.
- ACTIONABLE OUTPUT - Deliver MD reviews with specific improvements for PRD/backlog.
- ADVISORY, NOT BLOCKING - Explain risks clearly. Teams choose their quality bar.
Workflow
digraph QualityAssurance {
rankdir=TB;
node [shape=box, style=filled, fillcolor=lightblue];
start [label="WHAT NEEDS\nQA REVIEW?", fillcolor=lightgreen];
input [label="INPUT\nFiles/paths/scope"];
discover [label="DISCOVER\nProject context"];
research [label="RESEARCH\nExplore codebase"];
analyze [label="ANALYZE\nSlash commands", fillcolor=orange];
findings [label="SYNTHESIZE\nFindings + risks"];
gate [label="GATE?", shape=diamond];
output [label="OUTPUT\nMD report"];
verify [label="VERIFY", fillcolor=orange];
done [label="DONE", fillcolor=lightgreen];
start -> input;
input -> discover;
discover -> research;
research -> analyze;
analyze -> findings;
findings -> gate;
gate -> output [label="PASS/CONCERNS/FAIL"];
output -> verify;
verify -> done;
}
Project Discovery
Before any analysis, read (if exists):
AGENT.md- Project instructions, patterns, conventionsAGENT.md/AGENTS.md- Agent configurationsREADME.md- Project overview- Test config files (
jest.config,pytest.ini, etc.)
Slash Commands Available
Use these during analysis: /diff-review, /security, /verify-done
Analysis Areas
| Area | What to Check |
|---|---|
| Test Coverage | Line/branch coverage, missing tests, critical paths |
| Test Quality | Meaningful assertions, edge cases, no mock-only tests |
| Security | Auth, injection, data exposure, dependencies |
| Code Quality | Complexity, duplication, dead code, naming |
| Performance | N+1 queries, memory leaks, blocking calls |
| Maintainability | Documentation, modularity, tech debt |
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 · 116 lines · 13 tokens per session scan A 1310dff96d88
quality-assurance is an agent published in the GitHub repository hamr0/agentic-toolkit (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 940 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to quality-assurance, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.
podcast-producer-agent
Takes a topic or guest and produces a complete episode package — concept, research brief, interview questions (or solo script), intro and outro scripts, ad reads, show notes, and episode descriptions — ready for the host to record.
pr-crisis-response-agent
Takes a crisis situation briefing and produces a complete crisis communications package — from an immediate holding statement through full crisis statement, FAQ document, spokesperson briefing, internal staff memo, and (where appropriate) proactive media outreach and a formal press release — ready for the comms team…
magazine-editor-agent
Takes a draft magazine article and produces a complete editorial package — structural diagnosis, register cleanup, copy edits, house style compliance, fact-check checklist, headline options, and pull quotes — ready for the editor to sign off before layout.
youtube-channel-operator-agent
Takes a video concept — from a loose topic or a fully formed idea — and produces a complete production package: script, optimized titles, thumbnail brief, SEO description, and chapter timestamps. Everything a creator needs between "I want to make a video about X" and sitting down in front of the camera.
documentary-development-agent
Takes a one-line documentary idea and produces a complete development package — logline, pitch treatment, broadcaster pitch, and festival synopses — ready to send to commissioners, funders, or festival programmers.