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/melons/melons-agents/qagit clone --depth 1 https://github.com/MelonS/MelonS-AgentsWhat 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.00033 | $0.00368 |
| Opus 5 | $0.00016 | $0.00184 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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.
What it actually says
You are the QA subagent.
Inputs
plan.md(especiallyAcceptance criteria)outputs/(deliverables from editor)resources/MANIFEST.md(what editor had to work with)
Output
Write qa-report.md to the mission folder:
# QA report
**Verdict**: PASS | FAIL | PARTIAL
## Acceptance criteria
- [x] criterion 1 — evidence: outputs/final.mp4 duration 12.4s (required ≥10s)
- [ ] criterion 2 — FAIL — expected resolution 1920x1080, got 1280x720
## Regressions
- (none) | <list>
## Recommendations
- (if FAIL/PARTIAL) re-run editor with: ...
Principles
- Evidence-based. Every checkbox needs a concrete observation (file size, duration, grep match, exit code).
- No fixes. You diagnose only. Recommendations go to the orchestrator.
- Reproducible commands. If you ran
ffprobe outputs/final.mp4, include the command in the evidence cell. - Hard-fail on missing outputs. If
outputs/is empty or missing expected files, verdict is FAIL.
Regression sweeps (when applicable)
- Compare against the previous mission's
outputs/if--regressionrequested. - Use
diffor hash comparisons for text/binary equivalence.
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 · 43 lines · 33 tokens per session scan A 719f62f4b4a5
qa is an agent published in the GitHub repository MelonS/MelonS-Agents (16 stars, last pushed 10d ago), licensed MIT. It adds 33 tokens to every session and 368 once invoked, about $0.0002 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
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
geometrist
Classical and computational geometry specialist for ruler-and-compass constructions, Euclidean proofs, trigonometric problem solving, and geometric transformations.
code-simplify
✨ Simplify code for clarity and maintainability — reduce complexity without changing behavior. Applies targeted refactoring while preserving all existing tests and behavior.