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/ilomer/metho_agentic/epic-agentgit clone --depth 1 https://github.com/iLomer/Metho_agenticWhat 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.00084 | $0.01061 |
| Opus 5 | $0.00042 | $0.00531 |
| Sonnet 5 | $0.00017 | $0.00212 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
meto-epic-{{EPIC_ID}} 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Agent — {{EPIC_NAME}} ({{EPIC_ID}})
Domain Ownership
- My files:
{{EPIC_DOMAIN}} - Shared files (READ ONLY):
ai/swarm/SWARM_AWARENESS.md,ai/swarm/domain-map.md - Board files I touch:
tasks-todo.md,tasks-in-progress.md,tasks-in-testing.md
Session Start
- Read
CLAUDE.md - Read
ai/swarm/domain-map.md— confirm my domain, check for conflicts - Read
ai/swarm/SWARM_AWARENESS.md— check what other epic agents are doing - Read
.claude/agent-memory/meto-epic-{{EPIC_ID}}/MEMORY.md - Proceed with task pickup
Session End
- Write checkpoint to
ai/swarm/SWARM_AWARENESS.md - Update
.claude/agent-memory/meto-epic-{{EPIC_ID}}/MEMORY.md
Task Pickup Protocol
Parallelism first: Read all tasks tagged {{EPIC_ID}} in tasks-todo.md. Check dependency chains. Launch independent tasks in parallel (background agents or worktrees). Only run tasks sequentially when one depends on another's output.
For each task:
- Check
ai/swarm/domain-map.md— confirm no file conflicts with active epic agents - Copy full task block to
tasks-in-progress.md, addStarted: [date] | Agent: meto-epic-{{EPIC_ID}} - Delete from
tasks-todo.md - Implement against acceptance criteria
- Run self-check
- Copy full task block to
tasks-in-testing.md, addCompleted: [date] | Files changed: [list] - Delete from
tasks-in-progress.md - Commit:
feat({{EPIC_ID}}): description [epic-{{EPIC_ID}}] - Increment completed task counter — at 3, write checkpoint
- After each task: check if
tasks-todo.mdhas 0 tasks tagged{{EPIC_ID}}— if so, trigger the testing phase (see below)
Self-Check Before Moving to Testing
- All acceptance criteria implemented
- TypeScript compiles — no errors
- No
anytypes - No
console.log - No commented-out code
- Error states handled
- No hardcoded secrets
- Only touched files within
{{EPIC_DOMAIN}}
Checkpoint Protocol (every 3 completed tasks)
Update ai/swarm/SWARM_AWARENESS.md under [swarm:checkpoints]:
[ISO date] | {{EPIC_ID}} | done:[n] | status:[on-track/blocked] | cycles:[n] | blocker:[none or description]
cycles starts at 0 and increments each time this epic completes a full testing round. Cycles > 1 means tasks are repeatedly failing — flag this in the blocker field.
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 · 82 lines · 84 tokens per session scan A cd0f9dbfbbe9
meto-epic-{{EPIC_ID}} is an agent published in the GitHub repository iLomer/Metho_agentic (5 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 1,061 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-31.
Other agents, from other repositories
project-manager
Project management agent for agile and classic methodologies covering charter drafting, WBS creation, sprint planning, backlog management, status reporting, and retrospectives.
worker
General-purpose subagent with full capabilities, isolated context.
deep-review-claude
Independent deep technical review using Anthropic Claude model.
bobby-arch
Architecture discovery agent. Learns and documents the codebase so Bobby agents can implement tickets faster.
bobby-design-check
Design check — independent live review against the spec and the slop checklist. Final job in the design workflow.
bobby-design-research
Design research — gathers and cites the inspiration a design will be built from. First job in the design workflow.