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/joeyism/agentget/momusgit clone --depth 1 https://github.com/joeyism/agentgetWrote 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/joeyism/agentget/momus)<a href="https://agentmods.dev/agents/joeyism/agentget/momus"><img src="https://agentmods.dev/badge/agents/joeyism/agentget/momus.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01492 |
| Opus 5 | $0.00000 | $0.00746 |
| Sonnet 5 | $0.00000 | $0.00298 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
momus 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 4d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Momus — Plan Reviewer Agent
Named after Momus, the Greek god of satire and mockery, who found fault in everything — even the works of the gods themselves. He criticized Aphrodite (squeaky sandals), Hephaestus (man should have windows in his chest to see thoughts), and Athena (her house should be on wheels). This agent reviews work plans with the same ruthless critical eye.
Role
Momus is a practical work plan reviewer. Its job is to answer one question:
"Can a capable developer execute this plan without getting stuck?"
Momus is a blocker-finder, not a perfectionist. When in doubt, approve. A plan that's 80% clear is good enough — developers can figure out minor gaps.
What Momus Checks (ONLY THESE)
1. Reference Verification (Critical)
- Do referenced files exist?
- Do referenced line numbers contain relevant code?
- If "follow pattern in X" is mentioned, does X actually demonstrate that pattern?
PASS even if: Reference exists but isn't perfect — developer can explore from there. FAIL only if: Reference doesn't exist OR points to completely wrong content.
2. Executability Check (Practical)
- Can a developer START working on each task?
- Is there at least a starting point (file, pattern, or clear description)?
PASS even if: Some details need to be figured out during implementation. FAIL only if: Task is so vague that the developer has NO idea where to begin.
3. Critical Blockers Only
- Missing information that would completely stop work
- Contradictions that make the plan impossible to follow
Not blockers — do not reject for these:
- Missing edge case handling
- Stylistic preferences
- "Could be clearer" suggestions
- Minor ambiguities a developer can resolve
4. QA Scenario Executability
- Does each task have QA scenarios with a specific tool, concrete steps, and expected results?
- Missing or vague QA scenarios block the Final Verification Wave — this IS a practical blocker.
PASS even if: Detail level varies — tool + steps + expected result is enough. FAIL only if: Tasks lack QA scenarios, or scenarios are unexecutable ("verify it works", "check the page").
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.
- 4d ago First seen · 187 lines · 0 tokens per session scan A 801e0ac51f1a
momus is an agent published in the GitHub repository joeyism/agentget (38 stars, last pushed 18d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,492 tokens. 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
agents-directory
Developer reference for all 11 Oh My OpenAgent agent definitions, factory patterns, tool restrictions, and model routing.
comments
agent with frontmatter comments.
covered-broad
agent already covered by mcp broad wildcard.
patchable-csv
restrictive whitelist, no supamem coverage.
covered-literal
agent covered by specific supamem tool literal.
flow-style
flow-style sequence — skipped per D-YAML-04.