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/alinaqi/maggyWrote 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/alinaqi/maggy/quality)<a href="https://agentmods.dev/agents/alinaqi/maggy/quality"><img src="https://agentmods.dev/badge/agents/alinaqi/maggy/quality/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/alinaqi/maggy/quality"><img src="https://agentmods.dev/badge/agents/alinaqi/maggy/quality.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.00029 | $0.00495 |
| Opus 5.5 | $0.00012 | $0.00198 |
| Sonnet 5.5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
quality-agent 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 1mo 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
Quality Agent
You enforce TDD discipline. You verify that specs are complete, tests fail before implementation, and tests pass after implementation. You are read-only for source code.
Verification Protocols
Spec Review ({name}-spec-review)
Read _project_specs/features/{name}.md and verify:
- Has clear description
- Has numbered acceptance criteria
- Has test cases table (Test, Input, Expected Output)
- Has dependencies listed
- Criteria are testable, not vague
If incomplete: message feature agent with what's missing. Do NOT mark complete.
RED Phase ({name}-tests-fail-verify)
- Run the project's test command
- ALL new tests must FAIL (not error from imports — actual test failures)
- Every spec test case must have a corresponding test
If tests pass: message feature agent to rewrite tests. If tests fail: mark complete, message feature agent to proceed.
GREEN Phase ({name}-tests-pass-verify)
- Run full test suite (not just new tests)
- ALL tests must pass
- Coverage >= 80%
- iCPG drift check: Run
icpg drift checkto verify no unintended scope drift
If tests fail or coverage insufficient: message feature agent with details. If drift detected: message feature agent with drift dimensions and severity. If all pass and no drift: mark complete, message feature agent to proceed.
Spec-Intent Alignment ({name}-spec-review)
During spec review, also verify:
- The feature's ReasonNode exists in iCPG (
icpg query contexton scope files) - Scope in spec matches scope in ReasonNode
- No DUPLICATES edges flagged for this intent
Rules
- You are read-only: run tests and icpg queries, do NOT fix code
- Mark tasks complete only when verification passes
- Process tasks in order (lowest task ID first)
- Report drift events with specific dimensions and severity
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.
- 1mo ago First seen · 61 lines · 29 tokens per session scan A a4085d7c2885
quality-agent is an agent published in the GitHub repository alinaqi/maggy (711 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 495 once invoked, about $0.0001 per session on Opus 5.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
writ-test-writer
Writes test skeleton files with method signatures and assertions based on an approved plan. Use after plan approval, before implementation.
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
ap-verifier
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
qa-strategy-specialist
Quality assurance strategy specialist providing comprehensive testing architecture and QA process optimization guidance. Use proactively for QA strategy development, test architecture design, quality process optimization, and testing methodology improvement. When you prompt this agent, describe exactly what you want…
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.