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-quicknpx skills add febradc-github/turnstile --skill turnstile-quickgit 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-quick)<a href="https://agentmods.dev/skills/febradc-github/turnstile/turnstile-quick"><img src="https://agentmods.dev/badge/skills/febradc-github/turnstile/turnstile-quick.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.00049 | $0.00806 |
| Opus 5 | $0.00024 | $0.00403 |
| Sonnet 5 | $0.00010 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
turnstile-quick 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick
Process
- Search the vault for notes or existing tickets related to the description ($ARGUMENTS). If an open item already covers it, point there and stop.
- Assess triviality: estimate points. Above the quick_max_points ceiling, multiple deliverables, or an unresolved design choice -> refuse and route to
/turnstile:refine(quote the reason and the ceiling). Bug fixes handed off byturnstile-systematic-debuggerarrive with a confirmed root cause -- include it in the description. - Draft the item: clear title, one-paragraph description, 1-3 concrete acceptance criteria, points (1 up to the ceiling), assignee (
claudeunless told otherwise), type (taskby default;storyif user-facing scope). For a bug, note the root cause in the description and tag the item notebug. - Determine the destination:
turnstile/sprint.ymlexists and is active -> the item joins it withstatus: todoandadded_mid_sprint: true.- No active sprint ->
turnstile/backlog.ymlwithstatus: ready(no further gates needed); say the next/turnstile:sprint-planwill pick it up.
- Present the drafted item and destination; ask for one explicit approval. Revise on request. Write nothing until approved.
- Once approved: mint the id (scan
turnstile/backlog.yml,turnstile/sprint.yml,turnstile/sprints/*.ymlforC-<N>ids; new id isC-<max+1>), write the item note per the template reference, append the item to the destination, and confirm any [[wikilink]] added resolves (quick notes usually link nothing, which is fine). - Tell the user the item is in, and what runs it:
/turnstile:work <id>(or that it queues behind the currentin_progressitem -- one thing at a time).
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 · 35 lines · 49 tokens per session scan A 6f48d61ee639
turnstile-quick is a skill published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 806 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
specify-meta
Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.
feature-prioritization
RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.
user-story-generator
Transforms requirements into user stories with Given/When/Then acceptance criteria ready for sprint planning and Jira. Use when user needs to write user stories, create Jira tickets, define acceptance criteria, or says "user stories", "acceptance criteria", "sprint backlog", "Jira tickets", "as a user I want"…
ambiguity-resolver
Structures a brief HANDED DOWN by a stakeholder (boss, exec, another team) into a one-page problem statement with scope boundaries and a named decision owner. Use when the PM says "мне спустили задачу", "I've been asked to look into Y", "руководство хочет X", "CEO попросил разобраться" — a request the PM didn't…
project-init
Framework for creating project documentation from specs — reviews, research, architecture, planning, task decomposition into slices, and optional Jira sync. Triggers on "storm the spec", "analyze spec", "project init", "init project from spec", "проанализируй ТЗ", "разбери ТЗ", "создай документацию по ТЗ", or when…
lifecycle
Orchestrate feature lifecycle — track steps, enforce gates, dispatch sub-agents. Use when starting a new task, checking lifecycle status, or advancing to the next step.