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 skills add ebursztein/sprinty --skill using-sprintygit clone --depth 1 https://github.com/ebursztein/sprintyWrote 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/ebursztein/sprinty/using-sprinty)<a href="https://agentmods.dev/skills/ebursztein/sprinty/using-sprinty"><img src="https://agentmods.dev/badge/skills/ebursztein/sprinty/using-sprinty/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ebursztein/sprinty/using-sprinty"><img src="https://agentmods.dev/badge/skills/ebursztein/sprinty/using-sprinty.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.03009 |
| Opus 5.5 | $0.00025 | $0.01204 |
| Sonnet 5.5 | $0.00012 | $0.00602 |
| Haiku 4.5 | $0.00006 | $0.00301 |
Grade A, and why
using-sprinty 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 16d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Sprinty
Prefer compact commands first. Lists are compact and say which _get() tool returns full detail. Mutating tools return acknowledgements plus next_tools, concrete follow-up calls derived from live state; do not expect or request full sprint dumps from mutations.
Core Tools
| Tool | Input | Use |
|---|---|---|
info |
{ git_dir?, data_dir?, workspace_dirs?[] } |
First-call orientation before binding. Returns startup workflow, resume/create help, dashboard state, and sprint rows with title, created time, and open/closed/blocked item counts. |
sprint_resume |
{ git_dir, data_dir?, agent_token? } |
Rebind this MCP process to an existing sprint. Returns a bounded briefing (counts, current item, blocked ids, last resolved, recent notes), the skills to read, and the dashboard URL - use it instead of re-deriving state with overview+next. data_dir defaults to <git_dir>/.sprinty. Never call sprint_new as a resume trick. |
sprint_detach |
{} |
Clear this process binding before resuming a different sprint; only the sole attached agent may detach the connection. |
sprint_new |
{ goal, git_dir, data_dir?, context_notes?[], agent_token? } |
Start one sprint with explicit git_dir; data_dir defaults to <git_dir>/.sprinty. Returns the dashboard URL. |
overview |
{} |
Compact sprint title/details/artifacts/subsprints/items. Use this to orient. |
next |
{ past?=1, future?, future_per_subsprint?=1, include_high_priority?=true } |
Compact active work window. Prioritizes your claims, then unclaimed ready work; applies high-priority and per-subsprint window settings. Suggested work still needs an atomic claim. future caps the total returned across all subsprints. No full graph. |
search |
{ pattern, context_size?=512 } |
Regex search. Returns { id, type, text, tool_call }; use tool_call for full detail. |
dashboard_info |
{} |
Current localhost dashboard URL and port, or running:false when stopped. |
dashboard_restart |
{} |
Restart the dashboard server and return the new URL and port. |
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.
- 16d ago Changed · +32 lines 6e272b62ad3c
- 1mo ago Changed 097594922984
- 2mo ago First seen · 65 lines · 62 tokens per session scan A 499e444edfee
using-sprinty is a skill published in the GitHub repository ebursztein/sprinty (0 stars, last pushed 16d ago), licensed Apache-2.0. It adds 62 tokens to every session and 3,009 once invoked, about $0.0002 per session on Opus 5.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
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
create-issue
This skill should be used when the user asks to "create an issue", "file a bug", "report a problem", "rewrite an issue", or "improve an issue title or body".
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
spk-run-verdict-capture
Set a Spec Kitty work-package review verdict through the deterministic event-log seam, so every agent harness records approve/reject the same way.
spk-run-implement-review
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
spk-team-sync
Operate Spec Kitty tracker sync (sync pull/sync push/sync run for local providers) and hosted SaaS-backed mission data.