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.
git clone --depth 1 https://github.com/iLomer/Metho_agenticWrote 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/ilomer/metho_agentic/epic-agent)<a href="https://agentmods.dev/agents/ilomer/metho_agentic/epic-agent"><img src="https://agentmods.dev/badge/agents/ilomer/metho_agentic/epic-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ilomer/metho_agentic/epic-agent"><img src="https://agentmods.dev/badge/agents/ilomer/metho_agentic/epic-agent.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00084 | $0.01214 |
| Opus 5.5 | $0.00034 | $0.00486 |
| Sonnet 5.5 | $0.00017 | $0.00243 |
| Haiku 4.5 | $0.00008 | $0.00121 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 87 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
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 - Your final answer is your report — don't send a separate message to the lead
- 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). Run tasks sequentially when one depends on another's output, or when they touch the same files or the same feature.
Returned slice? If the block has a FAILED VALIDATION note, fix only the listed criteria — don't redo the passing ones.
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 - Write the failing tests first — one per acceptance criterion — then implement until they pass
- Run self-check — paste the test/typecheck/lint output into the block as
Verified: - Route by size:
- XS/S: copy to
tasks-done.mdwithCompleted: [date] | Files changed: [list] | Self-validated: PASS - M/L: copy to
tasks-in-testing.mdwithCompleted: [date] | Files changed: [list]
- XS/S: copy to
- 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)
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 Changed · +5 lines da5104b40976
- 1mo 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 2d ago), licensed MIT. It adds 84 tokens to every session and 1,214 once invoked, about $0.0003 per session on Opus 5.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.
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.
aiox-po
AIOX Product Owner autônomo. Valida stories, gerencia backlog, garante coerência de epic context. Usa task files reais do AIOX.
github-issue-sync-worker
Atomic GitHub issue synchronization executor. Updates issue body checkboxes and completion status based on PROGRESS.json changes.
Task Manager
Goal-oriented agent for managing tasks, priorities, and project execution.
planner
Turns architecture into a numbered, executable implementation plan with workstreams, file targets, and acceptance tests.