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-nextnpx skills add febradc-github/turnstile --skill turnstile-nextgit 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-next)<a href="https://agentmods.dev/skills/febradc-github/turnstile/turnstile-next"><img src="https://agentmods.dev/badge/skills/febradc-github/turnstile/turnstile-next.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.00050 | $0.00757 |
| Opus 5 | $0.00025 | $0.00378 |
| Sonnet 5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
turnstile-next 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 4d 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.
Next
Process
- Read the config.
cadence: sprint: explain and stop (see above). - Look at
turnstile/sprint.yml:- Absent: the flow board will be created in step 4.
- Active with
mode: flow: this is the board. - Active without
mode: flow: an active sprint predates the flow switch. Refuse to pull; tell the user to archive it first via/turnstile:sprint-plan(its flow-mode explainer offers the archive step). Never convert a live sprint in place.
- If the board has an item with
status: in_progressortodo, report it and stop -- flow pulls one piece of work at a time:in_progress-> finish it (/turnstile:review <id>);todo-> start it (/turnstile:work <id>). Do not pull a second item past a waiting one unless the user explicitly says to skip it (then proceed, leaving the todo in place). - Read
turnstile/backlog.ymland list the ready leaf items (excludetype: epicand anything named as aparent) in file order. The top item is the pull candidate; show it (id, title, points) with the next few queued behind it. No ready items: say the queue is empty and suggest/turnstile:refineor/turnstile:quick; if ready-looking work is stuck in an unbroken epic, point at/turnstile:breakdown <epic-id>. Stop. - Ask for one confirmation (the user may pick a different queued item -- their call). Once confirmed: create the flow board per the template if it does not exist, append the item with
status: todoandcarryovers: 0, and remove it fromturnstile/backlog.yml-- one live copy per item. - Search the vault for notes related to the pulled item's topic; surface anything relevant.
- Tell the user the item is on the board and
/turnstile:work <id>starts it.
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.
- 4d ago First seen · 33 lines · 50 tokens per session scan A fdf09a044df1
turnstile-next is a skill published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 757 once invoked, about $0.0003 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…
setup-initiative
Guides the PM through an initiative alignment checklist — metric, baseline, target, stakeholders, success/kill criteria. Use before a gate, when the PM says "setup initiative", "set the target", "define success criteria", "align on goals", or when the coverage map shows Frame incomplete. NOT a prerequisite for…
go
Execute the next undone task(s) from a sprint's TASKS.md by dispatching the magi-developer subagent (Sonnet by default). Updates WORKS.md as a development log. Pauses for user confirmation before any commit. Default behavior auto-parallelizes tasks with disjoint file scopes; --parallel forces parallel, --sequential…