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 skills add komluk/scaffolding --skill spec-reviewgit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/skills/komluk/scaffolding/spec-review)<a href="https://agentmods.dev/skills/komluk/scaffolding/spec-review"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/spec-review/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.
<a href="https://agentmods.dev/skills/komluk/scaffolding/spec-review"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/spec-review.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00914 |
| Opus 5 | $0.00023 | $0.00457 |
| Sonnet 5 | $0.00009 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
spec-review 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Verification
Guide for verifying that implementation matches spec artifacts.
Input Files
| File | Required | Purpose |
|---|---|---|
{specs_path}/design.md |
Yes | Requirements and scenarios to verify |
{specs_path}/tasks.md |
Yes | Completion checklist |
{specs_path}/proposal.md |
Optional | Original intent reference |
Path Enforcement: The specs_path MUST be .scaffolding/conversations/{UUID}/specs/ where {UUID} is a valid UUID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). NEVER use descriptive folder names.
Three Verification Dimensions
1. Completeness
Question: Are all tasks done and all requirements covered?
| Check | Method | Issue Level |
|---|---|---|
All checkboxes marked [x] |
Parse tasks.md | CRITICAL if incomplete |
| All requirements have code | Search codebase for keywords | CRITICAL if missing |
| All new files exist | Verify file paths from tasks | CRITICAL if missing |
2. Correctness
Question: Does the code do what the spec says?
| Check | Method | Issue Level |
|---|---|---|
| GIVEN/WHEN/THEN satisfied | Trace scenario through code | WARNING if divergent |
| Tests cover scenarios | Match test names to scenarios | WARNING if uncovered |
| Edge cases handled | Check error paths in code | WARNING if missing |
| Validation commands pass | Run pytest / npm run validate | CRITICAL if failing |
3. Coherence
Question: Does the code match design decisions?
| Check | Method | Issue Level |
|---|---|---|
| Design decisions followed | Compare Decisions section to code | WARNING if violated |
| Patterns consistent | Check naming, structure, style | SUGGESTION |
| No undocumented changes | Diff scope vs design scope | WARNING if extra |
| No design deviations | Cross-reference architecture | WARNING if different |
Verification Process
- Load artifacts - Read design.md, tasks.md, proposal.md
- Check completeness - Parse checkboxes, search for requirement implementations
- Check correctness - Trace each scenario through code, verify test coverage
- Check coherence - Compare decisions to implementation, check patterns
- Generate report - Summarize findings with issue levels
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.
- 9d ago First seen · 107 lines · 47 tokens per session scan A 9a189e3e9092
spec-review is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 914 once invoked, about $0.0002 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-30.
Other skills, from other repositories
turnstile-loop-start
Starts a goal-directed loop run -- asks for mode, initialises state.json, then dispatches loop-runner repeatedly until the success condition is met, max-iterations is reached, or an unrecoverable error occurs.
turnstile-loop-status
Reads turnstile/loops/ /state.json and renders the current phase, status, and full iteration history in the terminal.
turnstile-conversate
Entry point for natural-language turnstile requests -- classifies the message against board state, then answers directly or invokes the one matching skill (brainstorm, quick, refine, spec, sprint-plan, work, review, breakdown, drop, systematic-debugger, code-reviewer).
turnstile-brain-init
Opt-in bulk bootstrap of turnstile/code/ -- one linked note per source file. The default pipeline is lazy (code notes only for ticket-touched files, written when the ticket passes review); this is the eager exception. Dispatched by /turnstile:brain-init only.
turnstile-brain
Vault layout, the shared note format, and the check-the-brain-first mandate. Auto-loads whenever any turnstile skill starts new work or /turnstile:review is about to commit.
turnstile-breakdown
Decomposes an epic into stories or an oversized story into tasks; writes child designs and backlog entries after explicit approval. Gate 1a-b. Dispatched by /turnstile:breakdown, conversate routing, or refine only.