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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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/commands/fatihkan/badi/spec-check)<a href="https://agentmods.dev/commands/fatihkan/badi/spec-check"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/spec-check.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.1 | $0.00000 | $0.00431 |
| Opus 5 | $0.00000 | $0.00216 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
spec-check 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 today.
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.
What it actually says
Specification conformance command. Audits the current code against SPECIFICATION.md, detecting feature gaps and scope drift.
Required Tools
- Read (SPECIFICATION.md, source code)
- Grep (feature search)
- Glob (file scan)
- Agent (auditor agent)
- Bash (running tests)
Procedure (5 Steps)
Step 1: Load the Specification
- Read
docs/SPECIFICATION.md - Extract the core features (Must Have)
- List the acceptance criteria
- Identify the Non-Goals items
Step 2: Codebase Scan
For every "Must Have" feature:
- Search for the related code (functions, routes, components)
- Assess whether the acceptance criterion is met
- Check test coverage
Step 3: Drift Detection
Missing Features:
- Features in the spec but not found in the code
Scope Creep:
- Features in the code but NOT in the spec
- Things marked Non-Goals yet implemented anyway
Partial Implementations:
- Features started but not finished
- Implementations that fail the acceptance criteria
Step 4: Build the Conformance Report
A status per feature:
- DONE — Acceptance criteria met
- PARTIAL — Started but unfinished
- MISSING — Not implemented yet
- DRIFT — Implemented differently from the spec
Step 5: Action Suggestions
- Prioritized missing-feature list
- Scope-creep remediation suggestions
- TaskBoard.md update (new tasks for the gaps)
Output Format
=== BADI SPEC CONFORMANCE CHECK ===
Specification: docs/SPECIFICATION.md
Date: [date]
Conformance Rate: [percent]%
Must Have: [done]/[total]
Should Have: [done]/[total]
Could Have: [done]/[total]
MISSING Features:
- [feature name] — [status]
DRIFT Findings:
- [drift description]
SCOPE CREEP:
- [marked non-goal but implemented]
Next: [priority action]
=========================================
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.
- today First seen · 72 lines · 0 tokens per session scan A be97b9328680
spec-check is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 431 tokens. 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-06.
Other commands, from other repositories
sonarqube
Analyze SonarCloud quality issues for a specific PR.
review-pr
Perform a comprehensive code review of a pull request.
pr
Analyze changes, detect scope issues, and create a well-structured PR.
refactor
Analyze code for SOLID violations and suggest targeted improvements.
audit-codebase
Codebase health audit scoring 7 categories with progression plan.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.