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.
git clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/qa)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/qa"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/qa/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/qa"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/qa.svg" alt="Reviewed on agentmods" width="80" 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.1 | $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 5d 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 qa — 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 — 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.
- 5d ago First seen · 654 lines · 17 tokens per session scan A 46f82a198842
qa is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. 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. It is 100% identical to qa, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
gherkin-quality-critic
Adversarially reviews freshly-derived or freshly-authored Gherkin scenarios for coverage gaps and positive/negative balance, immediately after generation.
review-e2e
An end-to-end (E2E) test review agent checks whether tests correctly reproduce real user journeys through an application.
qa-engineer
QA engineer. Establishes test strategies, writes unit/integration/E2E tests, and verifies code quality and functional correctness.
e2e-tests-reviewer
Playwright E2E test quality review for locator strategies, Page Object Model, auto-waiting, network interception, and WordPress/WooCommerce test helpers.
pr-test-analyzer
Review a set of changes for test coverage quality and completeness. Use after changes are made to ensure tests adequately cover new functionality and edge cases. Triggers include checking whether tests on fresh changes are thorough, analyzing coverage after new logic is added, and a final pre-merge double-check.