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-boardnpx skills add febradc-github/turnstile --skill turnstile-boardgit 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-board)<a href="https://agentmods.dev/skills/febradc-github/turnstile/turnstile-board"><img src="https://agentmods.dev/badge/skills/febradc-github/turnstile/turnstile-board.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.00015 | $0.00488 |
| Opus 5 | $0.00008 | $0.00244 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
turnstile-board 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.
What it actually says
Board
Purpose
Renders the full board -- backlog plus active sprint -- as a readable snapshot, with no side effects.
Process
- Read
turnstile/backlog.yml(if it exists). Render its items as a table: id, title, type (epic/story/task; blank means story), status (idea/ready/done/dropped), points. Group hierarchically: each epic first, its children indented beneath it (and their tasks beneath them), then flat items. For every container, append child progress to its row:<done children>/<total children> done, counting children across the backlog,sprint.yml, andsprints/*.yml. Renderdroppeditems last, marked as cancelled. - Read the current board --
turnstile/sprint.yml(a sprint or amode: flowboard), or (legacy boards) the rootturnstile/sprint-*.ymlwithsprint.status: active. Render its goal (sprints only) and items as a table: id, title, parent (when set), status (todo/in_progress/review/done/dropped), points, carryovers, and a+marker on items withadded_mid_sprint: true. Then report scope honestly: total points, pointsdone, and -- if any item hasadded_mid_sprint: true-- "N of M points were added mid-sprint" so quiet scope growth stays visible. - If neither file exists yet, tell the user the board is empty and suggest
/turnstile:refine <idea>to start.
Inputs
turnstile/backlog.yml, turnstile/sprint.yml, turnstile/sprints/*.yml.
Outputs
None -- read-only.
Error handling
- Malformed YAML in a board file: surface the parse error and ask the user to fix it by hand -- never guess or auto-repair.
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 · 34 lines · 15 tokens per session scan A ff1fa0a4da4f
turnstile-board is a skill published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 488 once invoked, about $0.0001 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…