agentmods.dev

spec-score-mcp: Instructions file for Claude Code

CLAUDE.md

spec-score-mcp CLAUDE.md is an instructions file for Claude Code from openpoem/spec-score-mcp. It costs 306 tokens per session, scanned A, original, MIT.

A set of instructions for scoring specification files, which describe what a software project should do, and comparing those scores. It produces score tables, written verdicts, tips, and visual radar charts.

In plain words
What is it for?
Use it with /scan to score one specification and with /compare to assess two specifications side by side.
Why use it?
It gives a consistent way to review how complete or balanced a specification is and see how two specifications differ.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is openpoem/spec-score-mcp's own configuration. It tells Claude Code how to work on spec-score-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spec-score-mcp configures →

not rated 2repo 3mo ago A scan 306 tokens original MIT
View source ↗ openpoem/spec-score-mcp
Reuse

Borrowing it

Nothing to install: this file belongs to openpoem/spec-score-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/openpoem/spec-score-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/openpoem/spec-score-mcp

Made for: Claude Code.

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.

agentmods badge for spec-score-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/openpoem/spec-score-mcp/claude-md.svg)](https://agentmods.dev/instructions/openpoem/spec-score-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/openpoem/spec-score-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/openpoem/spec-score-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 306 This file is loaded in full into every session.
When invoked 306 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00306 $0.00306
Opus 5 $0.00153 $0.00153
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00031 $0.00031

Measured 8d ago against content hash cc872813216f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

spec-score-mcp CLAUDE.md 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.

CLAUDE.md · 31 lines

What it actually says

Spec Score MCP

Skills

/scan

Score a spec file and generate a visual radar chart.

  1. Read the file
  2. Score it: call spec_score with appropriate scores for the 4 axes
  3. Visualize it: call spec_visualize with the same scores
  4. Write <file>.scored.md containing only the results (NOT the original content):
    • A ## Spec Score heading with the source filename
    • Scores table (axis, score)
    • Balance score, verdict, and tip
    • The SVG as a base64 data URI in an <img> tag (NOT inline SVG — markdown renderers strip it)
    • To encode: btoa(svgString) → <img src="data:image/svg+xml;base64,..." alt="Spec Score" width="480" />

/compare

Compare two spec files side-by-side.

  1. Read both files
  2. Score both: call spec_score for each file separately
  3. Compare: call spec_compare with both sets of scores (left = first file, right = second file)
  4. Write compared.scored.md containing:
    • Summary of both files
    • The side-by-side SVG as a base64 data URI <img> tag (width="1000")
    • Scores table for both files
    • Verdict for each + comparison insight
Changes

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.

  1. 8d ago First seen · 31 lines · 306 tokens per session scan A cc872813216f

Subscribe to this mod's changes

spec-score-mcp CLAUDE.md is an instructions file published in the GitHub repository openpoem/spec-score-mcp (2 stars, last pushed 3mo ago), licensed MIT. It adds 306 tokens to every session, about $0.0015 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.

Analytics and metricsLLMPlanningclaudedenomcpmcp-serverspec
Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens