A cross-document consistency checker for software requirements, specifications, designs, plans, and task lists. It treats requirements.md as the main source of truth and can update downstream documents when they disagree.

Use it to check whether project documents trace back to the requirements and to align specifications, designs, plans, and tasks.

It finds mismatches between planning documents and corrects them before they cause implementation errors.

analyze — Command by Zts0hg

Install

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.

agentmods

npx agentmods add commands/zts0hg/codexspec/analyze

Clone the repo

git clone --depth 1 https://github.com/Zts0hg/codexspec

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,050 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00018	$0.01050
Opus 5	$0.00009	$0.00525
Sonnet 5	$0.00004	$0.00210
Haiku 4.5	$0.00002	$0.00105

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

Security

Grade A, and why

analyze 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 2d 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/commands/codexspec/analyze.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cross-Artifact Analyzer

Language Preference

Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English):

Interaction language (language.interaction): language for all conversation with the user — questions, explanations, status messages, and codexspec CLI terminal output.
Document language (language.document): language for generated artifact files (requirements/spec/plan/tasks).

Converse in the interaction language and author artifacts in the document language. Apply the project's translation standard to both: translate by meaning (not word-for-word), keep English for terms with no good native equivalent, and write as if originally in that language.

User Input

$ARGUMENTS

Operating Model

This command detects cross-artifact inconsistencies and auto-remediates them. It is not read-only.

requirements.md is the single source of truth. analyze never modifies requirements.md. Every fix conforms the downstream artifacts (spec.md, design.md, plan.md, tasks.md) to requirements.md; the fix direction is uniquely determined by the authority hierarchy (requirements > spec > design > plan > tasks) and never requires inventing intent.
Auto-apply deterministic, authority-directed fixes by default — both when invoked manually and when invoked inside the auto_next chain — with no confirmation prompt and no human-escalation path.

Resolve the feature by explicit path, then current branch. Ask the user if it is ambiguous; never select the latest feature silently.

Inputs

Load:

requirements.md
spec.md
design.md
plan.md
tasks.md
Constitution

A legacy feature may have no design.md; when it is absent, analyze the chain without the design link and proceed.

Legacy compatibility: if requirements.md is missing, state that the analysis starts at spec.md and cannot validate fidelity to the original discussion. In legacy mode there is no source of truth to conform to, so do not auto-modify artifacts; report findings only.

Read the full file on GitHub · 105 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.

2d ago First seen · 105 lines · 18 tokens per session scan A a47fc077b40e

Subscribe to this mod's changes

analyze is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 1,050 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.

Documents Localization Planning ai-assisted-development claude-code cli-tool i18n sdd

Create a LinkedIn post from any content source.

kanaerulabs/growth-kit · 9 tokens

analyze

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Cross-Artifact Analyzer

Language Preference

User Input

Operating Model

Inputs

What this file has done since we first saw it

Other commands, from other repositories

create-bucket-docs

chinese

english

en

translate-chapter

linkedin