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/fallow-rs/fallow/_templategit clone --depth 1 https://github.com/fallow-rs/fallowWhat 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.00013 | $0.00150 |
| Opus 5 | $0.00006 | $0.00075 |
| Sonnet 5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
agent-name 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 yesterday.
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
Brief role description. What is this agent's focus area?
What to check
- Area: What to look for
- Area: What to look for
Key files
path/to/relevant/files
Veto rights
Can BLOCK on:
- Critical issue specific to this agent's domain
Output format
End with a verdict:
## Verdict: APPROVE | CONCERN | BLOCK
What NOT to flag
- Out-of-scope concerns handled by other agents
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.
- yesterday First seen · 35 lines · 13 tokens per session scan A d2d5446c5d02
agent-name is an agent published in the GitHub repository fallow-rs/fallow (4,429 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 150 once invoked, about $0.0001 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
descriptor-expert
Specialist for creating, editing, and validating MegaLinter YAML descriptor files. Use when working on linter descriptors, adding new linters, or modifying linter configurations.
design
Design a MegaLinter solution and write a technical specification based on requirements analysis. Use after /analyze.
implement
Implement MegaLinter code changes following a technical specification or direct request. Use after /design, or directly for small focused changes.
megalinter-runner
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
analyze
Gather requirements for a MegaLinter change by asking clarifying questions until the problem is fully understood. Use before designing or implementing any change.
test-debugger
Debug failing MegaLinter linter tests. Use when tests fail, test fixtures need fixing, or Docker-based test execution needs troubleshooting.