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 skills/gsaranti/pantheon/metis-plan-tasknpx skills add gsaranti/pantheon --skill metis-plan-taskgit clone --depth 1 https://github.com/gsaranti/pantheonWrote 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/skills/gsaranti/pantheon/metis-plan-task)<a href="https://agentmods.dev/skills/gsaranti/pantheon/metis-plan-task"><img src="https://agentmods.dev/badge/skills/gsaranti/pantheon/metis-plan-task.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.1 | $0.00021 | $0.00870 |
| Opus 5 | $0.00010 | $0.00435 |
| Sonnet 5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
metis-plan-task 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/metis-plan-task
Produce one implementation plan for a free-text task description. The plan stays in chat; nothing is written to disk.
Arguments
- Trailing task — optional. What to plan: a
BUILD.mditem title, a more specific description of the next slice of an item already in progress, or free text. An item can take more than one plan → implement → review task to finish, so the argument can be narrower than the whole item;CURRENT.mdcarries what's left of an in-progress item. - No argument — present the
To builditems as a pick-one selector, with the active task fromCURRENT.md(the item in flight, or next up) as the recommended first option and an escape hatch for free text. Wait for the pick before planning. If there is no backlog and nothing active, ask plainly what to plan.
Context expected from session-start
.metis/CURRENT.md, .metis/SYNTHESIS.md, .metis/INDEX.md, and .metis/BUILD.md (when they exist) are expected to be in context already (loaded by /metis-session-start). SYNTHESIS.md is what's being built; BUILD.md holds the item's backlog entry; CURRENT.md's Active task and Current state say which item is live and, for an item already in progress, what's done and what's next; INDEX.md is the concept → source-doc map for finding the passages an item points at.
If any is missing — the session began without a session-start — read them lazily as the plan turns on them. Subsequent turns are cache hits.
Load (task-specific)
- The source-doc passages or code seams the item points at. Use the item's doc links (and
.metis/INDEX.mdfor concepts it names) to resolve source-doc paths, then read the docs there — that is where the architectural reasoning the plan must respect lives. .metis/CURRENT.md's Current state, when planning the next task of an item already in progress — so the plan covers what remains, not work already done.metis-code-explorersubagent dispatches when the surface is unfamiliar enough that planning would be guessing.metis-domain-researchersubagent when a plan step would commit to a technical choice the corpus does not cover.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 53 lines · 21 tokens per session scan A d2069c8cf7b9
metis-plan-task is a skill published in the GitHub repository gsaranti/pantheon (3 stars, last pushed 13d ago), licensed MIT. It adds 21 tokens to every session and 870 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-31.
Other skills, from other repositories
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.