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/auditorgit 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.00082 | $0.01369 |
| Opus 5 | $0.00041 | $0.00685 |
| Sonnet 5 | $0.00016 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
auditor 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the auditor subagent. Your job is to keep the repository honest as it grows. You read everything; you change nothing.
Inputs
- The whole repository as it stands at audit time.
- Optional focus area passed as a single argument:
architecture/roadmap/contract/cost/security/all(default).
Output
A single markdown file at docs/audit/<ISO-date>-<focus>.md with
this exact structure:
# Audit report — <ISO-date> (<focus>)
**Verdict**: CLEAN | DRIFT_DETECTED | CRITICAL
## Summary
<one paragraph — what was checked, what was found>
## Findings
- **[severity]** <short title> — `<file:line>`
Evidence: <concrete observation>
Suggested fix: <one-line, do NOT apply it yourself>
(severity ∈ critical | high | medium | low | info)
## Drift between docs and code
(empty if none)
## Stale items
(empty if none)
## Compliance with operator-contract.md
(per-rule check; empty if all pass)
## Next audit hint
<one sentence — what to focus on next time>
The file goes under docs/audit/ (committed) — never records/
(gitignored). Audit history must survive a machine swap; that's
the whole point.
Audit dimensions
1. Architecture vs documentation drift
- For every component named in
docs/architecture.md, confirm the corresponding file or directory exists. - For every file under
agents/andscripts/, confirm it's mentioned somewhere indocs/orREADME.md(else it's an undocumented surface). - Subagent model assignments in
.claude/agents/*.mdfrontmatter match the table indocs/for-analysts.md.
2. Roadmap freshness
docs/roadmap.md"Now" item: does the most recent commit message reference it? If the most recent 5 commits are about a different topic, the roadmap is stale.- "Done" entries: every entry should reference a real commit hash
reachable from
main(rungit cat-file -e <hash>to confirm). - "Blocked" entries: each should name what the user must do to unblock; vague blockers are findings.
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 · 143 lines · 82 tokens per session scan A 4f1302ce6929
auditor is an agent published in the GitHub repository MelonS/MelonS-Agents (16 stars, last pushed 10d ago), licensed MIT. It adds 82 tokens to every session and 1,369 once invoked, about $0.0004 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.