Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-build-spec)<a href="https://agentmods.dev/skills/gsaranti/pantheon/metis-build-spec"><img src="https://agentmods.dev/badge/skills/gsaranti/pantheon/metis-build-spec/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/skills/gsaranti/pantheon/metis-build-spec"><img src="https://agentmods.dev/badge/skills/gsaranti/pantheon/metis-build-spec.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.00025 | $0.00659 |
| Opus 5 | $0.00013 | $0.00329 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
metis-build-spec 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 10d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/metis-build-spec
Produce the build's two standing files: .metis/SYNTHESIS.md in its final form (what is being built) and .metis/BUILD.md (the ordered backlog of items that build it).
Preflight
Run references/build-spec-preflight.sh before drafting. It exits non-zero if .metis/BUILD.md already exists (surface the error, suggest the user delete the file manually if a fresh rewrite is intended, and stop). Otherwise it reports DOCS_PRESENT, RECONCILE_DONE, and WALK_PENDING.
Input shape
Determined from the preflight + the trailing prompt:
- Docs-first ready —
DOCS_PRESENT=yes,RECONCILE_DONE=yes,WALK_PENDING=no. Synthesize from the reconciled corpus. - Reconcile or walk pending —
RECONCILE_DONE=noorWALK_PENDING=yes. Suggest the prerequisite command (/metis-reconcileor/metis-walk-open-items) and proceed only if the user explicitly insists. - No docs —
DOCS_PRESENT=no. The trailing prompt is required; if absent, stop and ask. If present, classify as prompt-seeded (fresh project) or existing-codebase (delta on top of code in the repo) based on what the prompt describes.
Load
- For docs-first:
.metis/SYNTHESIS.md,.metis/INDEX.md, and the source docs underdocs/at the cited passages. - For existing-codebase: code from the source tree, via
metis-code-explorersubagent dispatches.
Do not load
.metis/CONTRADICTIONS.md,.metis/QUESTIONS.md,.metis/RESOLVED.md.
Read first
references/writing-build-spec.md — read before drafting.
Write scope
Two files:
.metis/SYNTHESIS.md— rewritten to its final standing form. When it already exists (docs-first, from reconcile),Readit before theWriteso the overwrite succeeds on the first attempt..metis/BUILD.md— created: the ordered backlog, every item under To build, Built empty.
Invocation prompt
Trailing prompt: see ${CLAUDE_PLUGIN_ROOT}/references/command-prompts.md.
Return
One message to the user:
What ships with it
2 files 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.
- 10d ago First seen · 54 lines · 25 tokens per session scan A 22135086bf73
metis-build-spec is a skill published in the GitHub repository gsaranti/pantheon (3 stars, last pushed 18d ago), licensed MIT. It adds 25 tokens to every session and 659 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:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
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: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: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…