spec-check

spec-check is a command for Claude Code from swingerman/engineer. It costs 21 tokens per session (89 once invoked), scanned A, original, MIT.

A review command that checks Given/When/Then acceptance-test specifications for implementation details that do not belong in behavior-focused requirements. GWT means describing what happens before, during, and after an action.

In plain words
What is it for?
Auditing one specification file or all text files in the specs directory for implementation leakage.
Why use it?
It helps keep acceptance specifications understandable and independent from the code's internal design.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the atdd plugin — 26 skills, 4 commands, 8 agents, 2 hooks, 1 plugin shipped together

Good fit Auditing one specification file or all text files in the specs directory for implementation leakage.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/swingerman/engineer/spec-check
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.

Clone the repo
git clone --depth 1 https://github.com/swingerman/engineer

Made for: Claude Code.

Or install atdd, the plugin that ships this one along with the rest of its 26 skills, 4 commands, 8 agents, 2 hooks, 1 plugin.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/swingerman/engineer/spec-check/github.svg)](https://agentmods.dev/commands/swingerman/engineer/spec-check)
Your own site
<a href="https://agentmods.dev/commands/swingerman/engineer/spec-check"><img src="https://agentmods.dev/badge/commands/swingerman/engineer/spec-check/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 spec-check

Your own site · 80×15
<a href="https://agentmods.dev/commands/swingerman/engineer/spec-check"><img src="https://agentmods.dev/badge/commands/swingerman/engineer/spec-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 89 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.00021 $0.00089
Opus 5.5 $0.00008 $0.00036
Sonnet 5.5 $0.00004 $0.00018
Haiku 4.5 $0.00002 $0.00009

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

Security

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

commands/spec-check.md · 14 lines

What it actually says

Audit acceptance test specifications for implementation leakage.

Invoke the spec-guardian agent to review spec files.

If a file path was provided as an argument, review only that file. If no argument was provided, review all .txt files in specs/.

Target: $ARGUMENTS

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 · 14 lines · 21 tokens per session scan A 54af27f69ae2

Subscribe to this mod's changes

spec-check is a command published in the GitHub repository swingerman/engineer (157 stars, last pushed 24d ago), licensed MIT. It adds 21 tokens to every session and 89 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-08-30.

Related

Other commands, from other repositories