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-pickupnpx skills add febradc-github/turnstile --skill turnstile-pickupgit 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-pickup)<a href="https://agentmods.dev/skills/febradc-github/turnstile/turnstile-pickup"><img src="https://agentmods.dev/badge/skills/febradc-github/turnstile/turnstile-pickup.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.00086 | $0.00739 |
| Opus 5 | $0.00043 | $0.00369 |
| Sonnet 5 | $0.00017 | $0.00148 |
| Haiku 4.5 | $0.00009 | $0.00074 |
Grade A, and why
turnstile-pickup 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pickup
Process
- Read the current board --
turnstile/sprint.yml(a sprint or amode: flowboard), or (legacy boards) the rootturnstile/sprint-*.ymlwithsprint.status: active. If none exists, tell the user and suggest/turnstile:sprint-plan(or/turnstile:nextincadence: flow). - Find the
in_progressitem. For it, report -- in this order:- What you were about to do: the most actionable open thread -- the last
notesentry (work passes, debug notes, review FAIL reasons), plus which acceptance criteria look unmet against the current diff (git status/git difffor uncommitted work-in-progress). - What was blocking: anything in the notes or the item note that reads as a blocker or open question -- surface it even if stale.
- Where it stands: id, title, status, work-pass count, and its criteria source (spec
SP-<n>, planPL-<n>, or inline). - Context links: the item note, its design/plan, and vault notes related to its topic (search_notes) -- especially
adr-*/AR-*notes and anything the last session's curator dispatches recorded.
- What you were about to do: the most actionable open thread -- the last
- An item with
status: reviewand noin_progressitem: an interrupted review session -- point at/turnstile:review <id>to resume it. - No in-progress item, but parked item(s) exist: offer to un-park the most recently parked one (highest
parked_at), reading its## Resumesection aloud first -- that is the context being restored. On confirmation: set itsstatusback toin_progress, removeparked_at, and appendunparkedto itsnotes; the## Resumesection stays in the item note as history. Declined: list the parked items and continue to step 5. - No in-progress and nothing parked (or un-park declined): say so and point at the natural next move -- the board's
todoitems (/turnstile:work <id>), or/turnstile:sprint-plan//turnstile:nextwhen the board is empty. - Finish with the single next command to run.
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 · 29 lines · 86 tokens per session scan A 65fe12ae243d
turnstile-pickup is a skill published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 739 once invoked, about $0.0004 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"…
spec
Turn a wireframe and everything already agreed into a written spec in traditional agile shape — an initiative broken into epics, epics into user stories with acceptance criteria, and themes as the labels that span them — presented as an interactive drill-down tree the user prunes, edits and annotates in the browser…
user-story-map
Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.
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…