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/sveritg/metis_ph/epidemiologistgit clone --depth 1 https://github.com/SVerITG/Metis_PHWrote 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/sveritg/metis_ph/epidemiologist)<a href="https://agentmods.dev/agents/sveritg/metis_ph/epidemiologist"><img src="https://agentmods.dev/badge/agents/sveritg/metis_ph/epidemiologist.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.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
epidemiologist 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 First seen · 50 lines · 0 tokens per session scan A bcb873fb0552
epidemiologist is an agent published in the GitHub repository SVerITG/Metis_PH (1 stars, last pushed today), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 522 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-09-04.
Other agents, from other repositories
implementer
Mechanical execution agent for bounded, well-defined tasks. Scope and approach must be explicit in the task prompt. Use after a planner has produced a plan. For complex logic or design decisions, use Sonnet instead.
task-decomposer
Task decomposition specialist who breaks PRDs and epics into atomic, estimable work items with clear acceptance criteria and done definitions. Sequences by dependencies, groups into milestones, sizes by complexity. Use when you say "decompose this PRD", "break into atomic tasks", or hand it a PRD or epic. Do NOT use…
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
nvim-navigator
Read-only code navigation and analysis specialist for a project open in vibing.nvim. Use for "where is X defined/used", "what calls this function", "what's the type of this", or "what diagnostics exist here" questions — it answers using the live Neovim buffer/LSP state via vibing-nvim MCP tools instead of editing…
Azure Logic Apps Expert Mode
Expert guidance for Azure Logic Apps development focusing on workflow design, integration patterns, and JSON-based Workflow Definition Language.
system-evolver
Evolves the Datacore system and MCP server. Evaluates new capabilities, determines the right form factor (MCP tool, agent, command, skill), and implements the conversion. Handles the full lifecycle: evaluate, build tool handler or agent definition, update module.yaml, update registry, deprecate old form, rebuild MCP…