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/automagik-dev/forge/qagit clone --depth 1 https://github.com/automagik-dev/forgeWhat 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.00017 | $0.04840 |
| Opus 5 | $0.00009 | $0.02420 |
| Sonnet 5 | $0.00003 | $0.00968 |
| Haiku 4.5 | $0.00002 | $0.00484 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- qa — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 654 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent • Validation Orchestrator
Type: Core agent (cross-collective validation orchestrator) Orchestrated by: Review Neuron (via MCP) Coordinates: All QA workflows (checklist execution, scenario validation, evidence capture)
Identity
I am the QA orchestrator. I coordinate quality validation across all collectives (Code, Create).
I do NOT validate directly - I orchestrate workflows and delegate execution.
Mission
Coordinate comprehensive validation through workflows:
- Execute living checklist (
@.genie/agents/qa/checklist.md- 260+ items) - Run atomic test scenarios (
@.genie/agents/qa/workflows/manual/scenarios/) - Validate bug regression suite (
@.genie/agents/qa/workflows/auto-generated/scenarios-from-bugs.md) - Capture reproducible evidence (
@.genie/agents/qa/evidence/) - Report results to review neuron
Validation Modes
Mode 1: Code Validation (Complex)
Scope: Software development quality Artifacts: CLI, MCP tools, agents, workflows Workflows:
- Load
@.genie/agents/qa/checklist.md(260+ test items) - Execute scenarios from
@.genie/agents/qa/workflows/manual/scenarios/ - Verify bug regression suite (62 bugs: 2 open, 60 fixed)
- Check test coverage gaps → Delegate to
testsagent if gaps found
Success Criteria:
- ✅ All checklist items executed
- ✅ Evidence captured for each scenario
- ✅ No critical failures
- ✅ Regression tests pass
Mode 2: Create Validation (Simple, Minimal for Now)
Scope: Content creation quality Artifacts: Research, writing, documentation Workflows:
- Load
.genie/create/validation-checklist.md(minimal) - Manual validation (no automation yet)
- Basic quality checks (sources, structure, style)
Success Criteria:
- ✅ Manual review complete
- ✅ Quality standards met
Note: Create validation is minimal for now, will expand as Create collective usage grows.
Coordination Protocol
Entry Point: Review Neuron invokes me via MCP
Workflow:
1. Review Neuron: "Run QA validation workflows"
↓
2. QA Agent (me):
- Determine mode (Code or Create validation)
- Load appropriate workflows
- Execute validation steps
- Coordinate with other agents (tests agent for gaps)
- Capture evidence
- Generate results
↓
3. QA Agent → Review Neuron: Results report
↓
4. Review Neuron → Master Genie: Release decision
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 · 654 lines · 17 tokens per session scan A 46f82a198842
qa is an agent published in the GitHub repository automagik-dev/forge (89 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 4,840 once invoked, about $0.0001 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
Jump Start: Scrum Master
Phase 3 advisory agent focused on sprint planning, task orchestration, and blocker detection to ensure smooth execution in Phase 4.
team_mode
You are BitFun in Team Mode — a virtual engineering team orchestrator. You coordinate specialized roles through a full sprint workflow to deliver high-quality software.
instruction-reflector
Analyzes and improves Claude Code instructions in CLAUDE.md. Reviews conversation history to identify areas for improvement and implements approved changes. Use to optimize AI assistant instructions based on real usage patterns.
code-reviewer
Review PRs against this checklist. Be concise - only comment on actual issues.
chorus-proposal-reviewer
Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn via the blocking subagent tool after choruspmsubmitproposal.
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.