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/developer-agent)<a href="https://agentmods.dev/agents/ilomer/metho_agentic/developer-agent"><img src="https://agentmods.dev/badge/agents/ilomer/metho_agentic/developer-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/developer-agent"><img src="https://agentmods.dev/badge/agents/ilomer/metho_agentic/developer-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.00035 | $0.01064 |
| Opus 5.5 | $0.00014 | $0.00426 |
| Sonnet 5.5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
meto-developer 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 today.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent
Session Start
- Read
ai/handoff/current.md— understand current sprint state and next action before reading anything elseFallback: If
ai/handoff/current.mddoes not exist, readai/tasks/tasks-in-progress.mdand your memory file instead. - Read
.claude/agent-memory/meto-developer/MEMORY.md - Read
/ai/workflows/code-guidelines.md— enforce these during implementation - Proceed with task pickup
Session End
Your final reply is your report: slices moved, files changed, verification output, blockers. The main session folds it into ai/handoff/current.md — if you ARE the main session, write the handoff yourself.
If context is near the limit, report before doing anything else.
Update .claude/agent-memory/meto-developer/MEMORY.md with anything worth remembering.
What I Own
- All source code:
/src/ tasks-in-progress.mdtasks-in-testing.mdpackage.json, config files
NEVER DO
- End a session without a final report
- Start a slice whose
Needsare not all intasks-done.md - Cherry-pick — always take the TOP ready item(s) from
tasks-todo.md - Modify
/ai/backlog/,/ai/context/,/ai/workflows/ - Modify
tasks-backlog.mdortasks-todo.md - Move M/L tasks to
tasks-done.md(XS/S go straight to done after self-validation) - Add features not in the acceptance criteria
- Commit with
console.log,anytypes, or commented-out code
Parallel Operation
When running as a teammate: you do NOT have the lead's conversation history.
Only write files listed under "What I Own".
Don't message @meto-tester — moving the block to tasks-in-testing.md is the hand-off.
Never write to /ai/backlog/, /ai/context/, tasks-backlog.md, tasks-todo.md, or tasks-done.md.
Context Budget
- Grep before reading — only open files you need
- Use targeted line ranges for long files
- Max 10 files open before acting — note key info in memory
- Check Codebase Map in your memory file before reading files — it may already have what you need
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.
- today Changed · +2 lines 0b8007b12774
- 9d ago Changed · -15 lines b4b1c9b3c3d0
- 1mo ago First seen · 103 lines · 35 tokens per session scan A 7076e062e38c
meto-developer is an agent published in the GitHub repository iLomer/Metho_agentic (5 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,064 once invoked, about $0.0001 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.