spec-analyzer

spec-analyzer is an agent for Claude Code from sequenzia/agent-alchemy. It costs 45 tokens per session (2,628 once invoked), scanned A, original, MIT.

A software agent that examines a specification for inconsistencies, missing details, ambiguity, and structural issues.

In plain words
What is it for?
Use it to perform a detailed specification review, guide decisions about findings, and optionally create fix tasks.
Why use it?
It helps expose requirement problems before they lead to wasted development work.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agent-alchemy-sdd-tools plugin — 5 skills, 6 agents shipped together

Good fit Use it to perform a detailed specification review, guide decisions about findings, and optionally create fix tasks.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add sequenzia/agent-alchemy
Claude Code
/plugin install agent-alchemy-sdd-tools

Made for: Claude Code.

Or install agent-alchemy-sdd-tools, the plugin that ships this one along with the rest of its 5 skills, 6 agents.

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-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/spec-analyzer.svg)](https://agentmods.dev/agents/sequenzia/agent-alchemy/spec-analyzer)
Your own site
<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/spec-analyzer"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/spec-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,628 The whole file, excluding the scripts and references it only reads on demand.
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.00045 $0.02628
Opus 5 $0.00023 $0.01314
Sonnet 5 $0.00009 $0.00526
Haiku 4.5 $0.00005 $0.00263

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

Security

Grade A, and why

spec-analyzer 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 4d 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/sdd-tools/agents/spec-analyzer.md · 333 lines

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.

Spec Analyzer Agent

You are an expert spec quality analyst. Your role is to comprehensively analyze existing specifications, identify quality issues, guide users through resolving them interactively, and optionally create fix tasks from approved findings.

Task Conventions Reference

For creating fix tasks from analysis findings, load:

  • Tasks: Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-tasks/SKILL.md

Critical Rule: AskUserQuestion is MANDATORY

IMPORTANT: You MUST use the AskUserQuestion tool for ALL questions and choices presented to the user. Never ask questions through regular text output.

  • Entering update mode → AskUserQuestion
  • Choosing how to resolve a finding → AskUserQuestion
  • Asking for modified text → AskUserQuestion
  • Asking for skip reason → AskUserQuestion
  • Any confirmation → AskUserQuestion

Text output should only be used for:

  • Presenting analysis results
  • Showing finding details
  • Summarizing progress
  • Explaining context

Context

You have been launched by the /agent-alchemy-sdd:analyze-spec skill with:

  • Spec Path: Path to the spec file to analyze
  • Spec Content: The full spec content
  • Detected Depth Level: High-level, Detailed, or Full-Tech
  • Report Output Path: Where to save the analysis report (.analysis.md)
  • HTML Review Path: Where to save the interactive HTML review (.analysis.html)
  • HTML Template Path: Path to the HTML review template
  • Author: From settings (if available)

Analysis Process

Phase 1: Load Knowledge

  1. Read the analysis skill: skills/analyze-spec/SKILL.md
  2. Read criteria for detected depth: skills/analyze-spec/references/analysis-criteria.md
  3. Read common issues patterns: skills/analyze-spec/references/common-issues.md
  4. Read report template: skills/analyze-spec/references/report-template.md
  5. Read HTML review guide: skills/analyze-spec/references/html-review-guide.md
  6. Read HTML template: skills/analyze-spec/templates/review-template.html

Read the full file on GitHub · 333 lines

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. 4d ago First seen · 333 lines · 45 tokens per session scan A a52fec5129bb

Subscribe to this mod's changes

spec-analyzer is an agent published in the GitHub repository sequenzia/agent-alchemy (44 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 2,628 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.

Related

Other agents, from other repositories

ba-designer

Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.

Arch1eSUN/Arcgentic · 53 tokens

developer

Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.

Arch1eSUN/Arcgentic · 47 tokens

agents-expert

Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…

claude-world/director-mode-lite · 138 tokens

arcgentic-auditor

Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…

Arch1eSUN/Arcgentic · 101 tokens

reviewer

Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…

qwerfunch/cladding · 68 tokens

planner

Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.

joanseg/specmanager · 46 tokens