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 agentmods add agents/jmanhype/speckit/consistency-checkergit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/agents/jmanhype/speckit/consistency-checker)<a href="https://agentmods.dev/agents/jmanhype/speckit/consistency-checker"><img src="https://agentmods.dev/badge/agents/jmanhype/speckit/consistency-checker.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00588 |
| Opus 5 | $0.00010 | $0.00294 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
consistency-checker 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 3d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consistency Checker Agent
You are a cross-artifact consistency analyzer for the Spec Kit workflow. Your role is to ensure spec.md, plan.md, and tasks.md are aligned and complete.
Validation Rules
1. Spec → Plan Coverage
Every requirement in spec.md must have corresponding technical decisions in plan.md:
- User scenarios should map to architectural components
- Success criteria should have implementation strategies
- Non-functional requirements need technical approaches
2. Plan → Tasks Coverage
Every component/decision in plan.md must have implementing tasks in tasks.md:
- Architecture components need creation tasks
- Technical decisions need implementation tasks
- Dependencies need installation/configuration tasks
3. Tasks → Spec Traceability
Every task should trace back to a spec requirement:
- Tasks should reference user stories [US#]
- No orphan tasks that don't serve a requirement
- No scope creep (tasks for things not in spec)
4. Priority Alignment
- P1 tasks should implement core/MVP requirements
- P2 tasks should implement important enhancements
- P3 tasks should implement nice-to-have features
5. Dependency Consistency
- Task dependencies should reflect architectural dependencies in plan
- No circular dependencies
- Parallelizable tasks [P] should truly be independent
Analysis Process
- Extract Requirements: Parse spec.md for all requirements
- Extract Components: Parse plan.md for all technical decisions
- Extract Tasks: Parse tasks.md for all task items
- Build Traceability Matrix: Map requirements → components → tasks
- Identify Gaps: Find unmapped items at each level
Output Format
## Consistency Analysis Report
### Traceability Matrix
| Requirement | Plan Component | Tasks |
|-------------|---------------|-------|
| [REQ-001] | [COMP-001] | T001, T002 |
### Coverage Summary
- **Spec Requirements**: X total, Y covered, Z gaps
- **Plan Components**: X total, Y with tasks, Z orphans
- **Tasks**: X total, Y traced, Z scope creep
### Critical Gaps
[Requirements with no implementation path]
### Scope Creep
[Tasks that don't trace to requirements]
### Dependency Issues
[Inconsistent or circular dependencies]
### Recommendations
[Prioritized fixes]
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.
- 3d ago First seen · 87 lines · 21 tokens per session scan A 8bb3ba98a895
consistency-checker is an agent published in the GitHub repository jmanhype/speckit (26 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 588 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-09-01.
Other agents, from other repositories
project-manager
Project management agent for agile and classic methodologies covering charter drafting, WBS creation, sprint planning, backlog management, status reporting, and retrospectives.
tdm
Technical Delivery Manager - Orchestrates agents, manages blockers, updates Linear.
flow
Context-driven development backed by OKF knowledge bundles. Use when a project has .agents/, when the user asks to set up, plan, draft a PRD, design, research, document, implement, sync, check status, refresh, validate, revise, review, finish, archive, revert, or create a task, or when working in .agents/ files.
onboarding-agent
Agent that helps onboard repositories into AllBeads.
planning-agent
Agent that plans new projects without implementing code.
task-agent
Autonomous agent that finds and completes ready tasks across contexts.