Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add febradc-github/turnstile/plugin install 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-sprint-plan)<a href="https://agentmods.dev/skills/febradc-github/turnstile/turnstile-sprint-plan"><img src="https://agentmods.dev/badge/skills/febradc-github/turnstile/turnstile-sprint-plan.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.1 | $0.00048 | $0.01188 |
| Opus 5 | $0.00024 | $0.00594 |
| Sonnet 5 | $0.00010 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
turnstile-sprint-plan 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 7d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Plan
Process
- Find the current sprint:
turnstile/sprint.yml, or (legacy) the rootturnstile/sprint-<N>.ymlwithsprint.status: active. If one exists and isactive:- Set its
sprint.statustocompleted. - Move it to
turnstile/sprints/sprint-<N>.yml(Nfromsprint.number, or parsed from itsname; createsprints/if missing). Move any other legacy rootsprint-*.ymlfiles there too -- one-time migration. - Collect every item in it whose
statusis notdoneordropped. - If any collected item's
carryoversis already 2 or more, dispatchbrain-curatorwith that observation -- a repeatedly-slipping item is worth remembering.
- Set its
- Search the vault for process-type notes relevant to sprint planning -- especially estimation bias or recurring blockers. Surface anything relevant, including conflicts.
- List the
readycandidates fromturnstile/backlog.yml(leaf items only -- excludetype: epicand anything named as aparent), each with id, title, and points, grouped under its parent epic/story when it has one. Mark which items you recommend pulling in, one-line reason each, ranked by:- Capacity first. Budget = points completed in the just-archived sprint, minus the points of carried-over items. No prior sprint means no velocity data -- say so and recommend a deliberately small starting set.
- Finish what's started. Children of an epic with done or carried-over children come first; closing an epic beats opening a new one.
- Coherence. Prefer items sharing one epic -- a focused sprint yields a natural goal.
- Age. Break ties by oldest
updateddate, so old ready items don't starve. Present the recommendation as a default the user can accept in one word, adjust, or replace. The user always has the final pick.
- Propose a one-line sprint goal derived from the selection and ask the user to confirm it or state their own. Do not proceed without explicit confirmation.
- Compute the new sprint number: previous
N+ 1 (highest acrossturnstile/sprints/and legacy files), or1. - Write
turnstile/sprint.ymlper the template reference: carried-over items first (carryoversincremented, prior status and notes unchanged), then newly selected items (status: todo,carryovers: 0). - Remove every newly selected item from
turnstile/backlog.yml(carried-over items were never there -- they came from the old sprint file, already archived). - Tell the user the new sprint is open, stating its goal and items.
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.
- 7d ago First seen · 43 lines · 48 tokens per session scan A 1e84011a5176
turnstile-sprint-plan is a skill published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,188 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
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…
incident-management
Runs an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes.…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
head-of-pmo
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.