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 narrative-quality-scorergit 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/narrative-quality-scorer)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/narrative-quality-scorer"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/narrative-quality-scorer/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/narrative-quality-scorer"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/narrative-quality-scorer.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.00037 | $0.02188 |
| Opus 5 | $0.00018 | $0.01094 |
| Sonnet 5 | $0.00007 | $0.00438 |
| Haiku 4.5 | $0.00004 | $0.00219 |
Grade A, and why
narrative-quality-scorer 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 8d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Quality Scorer
Purpose
Given a prompt text or file path, score it against the structural efficiency patterns identified by session-retrospective-miner. Returns a quality score (0–100) and specific diff-style improvement suggestions with token-efficiency justification for each.
This is the per-prompt complement to session-retrospective-miner's cross-session aggregate view.
Input
Provide one of:
Option A — inline text:
Score this narrative:
"Implement Phase 312: Analytics Export Module.
Read phase spec from 04-planning/phases/phase-312-analytics-export.md.
Create branch phase-312-analytics-export from main.
Implement: migration, entities, DTOs, service, controller, module."
Context: claudius-maximus-phase-implementation
Option B — file path:
Score the narrative at: 04-planning/phases/phase-312-analytics-export.md
Context: claudius-maximus-phase-implementation
Option C — batch:
Score all phase specs in: 04-planning/phases/
Context: claudius-maximus-phase-implementation
Output: summary table + worst-3 individual reports
Scoring Rubric
Each element is worth points because it correlates with measured session efficiency improvements. Scores are additive; maximum base score is 80, with up to +20 bonus points for a total of 100.
| Element | Points | Efficiency Basis |
|---|---|---|
| Explicit insertion points (e.g., @AI:NAV anchors) | +15 | −8 turns avg per session when present |
| Acceptance criteria ("Done when X") | +12 | −8 turns avg per session when present |
| Explicit file paths to create/edit | +10 | −5 turns first-productive-turn |
| DB/convention reminders (PK type, column types) | +8 | Eliminates schema clarification loops (~23% of CM sessions) |
| Test commands specified | +8 | Reduces test-command clarification turns |
| Stop conditions for Agent spawns | +10 | −40% sub-agent turns when explicit |
| Anti-patterns explicitly excluded | +7 | Prevents known wrong paths |
| Branch naming convention | +5 | Baseline clarity |
| Module/feature type specified | +5 | Baseline clarity |
| Total possible | 80 | (+20 bonus for exceptional clarity) |
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.
- 8d ago First seen · 283 lines · 37 tokens per session scan A 3255b8a3b1ed
narrative-quality-scorer is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 2,188 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
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.
critique-visual-hierarchy
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).
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).
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).