speckit-analyze

speckit-analyze is a skill for Claude Code from wildcard/caro. It costs 32 tokens per session (2,403 once invoked), scanned A, original, AGPL-3.0.

A consistency checker for a feature specification, implementation plan, and task list. It reviews these documents together without changing them.

In plain words
What is it for?
It is for checking whether project documents agree before development starts.
Why use it?
It helps reveal contradictions, missing details, and quality problems after tasks have been created.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit It is for checking whether project documents agree before development starts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wildcard/caro/speckit-analyze
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.

Any agent
npx skills add wildcard/caro --skill speckit-analyze
Clone the repo
git clone --depth 1 https://github.com/wildcard/caro

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 speckit-analyze

README.md
[![agentmods](https://agentmods.dev/badge/skills/wildcard/caro/speckit-analyze/github.svg)](https://agentmods.dev/skills/wildcard/caro/speckit-analyze)
Your own site
<a href="https://agentmods.dev/skills/wildcard/caro/speckit-analyze"><img src="https://agentmods.dev/badge/skills/wildcard/caro/speckit-analyze/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.

agentmods 80×15 button for speckit-analyze

Your own site · 80×15
<a href="https://agentmods.dev/skills/wildcard/caro/speckit-analyze"><img src="https://agentmods.dev/badge/skills/wildcard/caro/speckit-analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,403 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 unknown 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.00032 $0.02403
Opus 5.5 $0.00013 $0.00961
Sonnet 5.5 $0.00006 $0.00481
Haiku 4.5 $0.00003 $0.00240

Measured 1mo ago against content hash 2eef0fbff6ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speckit-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 1mo 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/skills/speckit-analyze/SKILL.md · 261 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 1mo ago First seen · 261 lines · 32 tokens per session scan A 2eef0fbff6ca

Subscribe to this mod's changes

speckit-analyze is a skill published in the GitHub repository wildcard/caro (40 stars, last pushed today), licensed AGPL-3.0. It adds 32 tokens to every session and 2,403 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories

create-github-issue

Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.

tailcallhq/forgecode · 63 tokens

codexkit-safe-pi-planning

Facilitate SAFe 6.0 PI Planning events. Structure the 2-day cadence, generate PI Objectives with Business Value scores, build the Program Board for dependency visualization, and run the Confidence Vote. Use before every Program Increment when the organization follows SAFe.

hoavdc/CodexKit · 63 tokens

codexkit-process-mapper

Map existing business processes using BPMN 2.0 notation or simplified swimlane diagrams. Identify waste, handoffs, decision points, and improvement opportunities using Lean principles (8 Wastes). Use when documenting workflows for SOP creation, automation assessment, or process improvement. Do not use for software…

hoavdc/CodexKit · 73 tokens

codexkit-sprint-planning-assistant

Facilitate sprint planning by organizing backlog items, estimating effort, balancing capacity, identifying dependencies, and producing a sprint commitment summary. Use when teams need structured sprint planning output. Do not use for strategic roadmap planning, annual budgeting, or product vision work.

hoavdc/CodexKit · 61 tokens

codexkit-finance-close-coordinator

Organize month-end or quarter-end close blockers, reconciliations, owners, and evidence gaps into a routine control pack. Use when the work is finance close coordination and issue tracking. Do not use for accounting judgment, policy interpretation, or final technical accounting conclusions.

hoavdc/CodexKit · 62 tokens

codexkit-hiring-ops-coordinator

Package interview loops, schedules, feedback follow-ups, and candidate next steps for recruiting operations. Use when the work is routine hiring coordination and recap packaging. Do not use for final hiring decisions, compensation judgment, or sensitive people-policy advice.

hoavdc/CodexKit · 57 tokens