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 skills/febradc-github/turnstile/turnstile-specnpx skills add febradc-github/turnstile --skill turnstile-specgit clone --depth 1 https://github.com/febradc-github/turnstileWrote 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/febradc-github/turnstile/turnstile-spec)<a href="https://agentmods.dev/skills/febradc-github/turnstile/turnstile-spec"><img src="https://agentmods.dev/badge/skills/febradc-github/turnstile/turnstile-spec.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.00043 | $0.00796 |
| Opus 5 | $0.00022 | $0.00398 |
| Sonnet 5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
turnstile-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 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec
Process
- Look up
<id>(from$ARGUMENTS) inturnstile/backlog.ymland apply the refusals above. - Read the item's design doc:
turnstile/designs/DS-<n>.md(<n>from<id>=C-<n>), falling back to legacy names (turnstile/designs/<id>-*-design.md,turnstile/designs/<id>.md). - Search the vault for notes related to
<id>'s topic. Surface anything relevant, including conflicts, before continuing. - If a spec file for
<id>already exists (status is stillidea, so it can only be a draft from an abandoned prior session), warn the user and ask whether to overwrite or keep it. Never overwrite silently. - Write
turnstile/specs/SP-<n>.mdper the template reference. - Present the spec content and ask for explicit approval. Revise and re-present until approved.
- Once approved, update the item in
turnstile/backlog.yml:status: ready,updated= today. The spec file is the sole home of the criteria -- never copy them into YAML (remove a legacyacceptance_criteriafield if present). Update the item's note (US-<n>/TK-<n>): add- Spec: [[SP-<n>]], add the spec torelated, setupdatedto today. (A legacy item with no note: create one per the turnstile-brain item-note format.) Confirm every added [[wikilink]] resolves (list_unresolved_links). - Tell the user the item is
readyfor/turnstile:sprint-plan.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 33 lines · 43 tokens per session scan A cd73ac6a301c
turnstile-spec is a skill published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 796 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.
Other skills, from other repositories
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
implement-factory
Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
scenario-planning
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…
ai-ml-governance
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…
ai-research-analyst
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a…