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 skills add mattmre/EVOKORE-MCP-PUBLIC --skill phase-spec-optimizergit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/phase-spec-optimizer)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/phase-spec-optimizer"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/phase-spec-optimizer/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/mattmre/evokore-mcp-public/phase-spec-optimizer"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/phase-spec-optimizer.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.00040 | $0.03288 |
| Opus 5 | $0.00020 | $0.01644 |
| Sonnet 5 | $0.00008 | $0.00658 |
| Haiku 4.5 | $0.00004 | $0.00329 |
Grade A, and why
phase-spec-optimizer 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 7d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Spec Optimizer
Purpose
Analyzes a batch of completed phase specs against their actual session outcomes and produces an updated spec template with structural improvements baked in. Optionally applies the improved template to remaining unstarted phase specs.
This is the multi-phase product-development companion to narrative-quality-scorer. Where the scorer evaluates a single prompt, this skill compares an entire batch of phase specs against their real session data and produces a template diff you can apply forward.
Completed Phase Specs ──► Phase Spec Optimizer ──► Template Diff
+ │
Session JSONL ▼
+ Improved template + evidence
Retrospective Output │
+ ▼
Narrative Scores (Optional) Bulk-apply to
remaining unstarted specs
When To Use This Skill
Trigger it when:
- Starting a new block of phases (e.g., "next 20 phases of Claudius Maximus")
- Session efficiency has been declining across recent phases
narrative-quality-scorerflags the same missing elements repeatedly- Post-milestone — before planning the next milestone's phase specs
- After running
session-retrospective-minerand seeing a HIGH action item about phase spec structure
Prerequisites
This skill composes output from the Phase B retrospective skills plus two MCP tools:
session_analyze_replay— tool usage + retry signals per sessionsession_work_ratio— evidence/replay density per sessionsession-retrospective-minerskill — aggregate efficiency findingsnarrative-quality-scorerskill — per-spec quality scoring
Verify the tools are available with discover_tools before running.
Input Parameters
phase_range: "300-310" # completed phases to analyze (inclusive)
remaining_phases: "311-317" # unstarted phases to optionally update
project_path: "D:/GITHUB/Claudius-Maximus"
session_filter: "Claudius-Maximus" # project slug used in ~/.claude/projects/
apply_template: false # if true, apply improved template to remaining phase specs
template_path: "04-planning/phase-spec-template.md" # optional; auto-detected if omitted
phase_file_glob: "04-planning/phases/phase-*.md" # where phase spec files live
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.
- 7d ago First seen · 333 lines · 40 tokens per session scan A 27b5231662a8
phase-spec-optimizer is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 3,288 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
law-of-common-region
Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.
presentation-deck
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
accessibility-test-plan
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use accessibility-audit (design-systems).
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).