spec

A command that turns an approved design document into a detailed specification file. The specification must be explicitly approved before it is marked ready.

In plain words
What is it for?
Use it after agreeing on a design to record the expected behaviour and make the work ready for the next stage of the turnstile workflow.
Why use it?
It adds a review checkpoint between a design and implementation, so work does not proceed from an unconfirmed description.

Command

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.

agentmods
npx agentmods add commands/febradc-github/turnstile/spec
Clone the repo
git clone --depth 1 https://github.com/febradc-github/turnstile
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 86 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00038 $0.00086
Opus 5 $0.00019 $0.00043
Sonnet 5 $0.00008 $0.00017
Haiku 4.5 $0.00004 $0.00009

Measured yesterday against content hash 2b9f55780466, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.md · 8 lines

What it actually says

Use the Skill tool to invoke the turnstile-spec skill, passing $ARGUMENTS and the rest of this message unchanged.

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. yesterday First seen · 8 lines · 38 tokens per session scan A 2b9f55780466

Subscribe to this mod's changes

spec is a command published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 86 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-31.