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/leonhoffmann86/team-sprint/ticketnpx skills add leonhoffmann86/team-sprint --skill ticketgit clone --depth 1 https://github.com/leonhoffmann86/team-sprintWrote 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/leonhoffmann86/team-sprint/ticket)<a href="https://agentmods.dev/skills/leonhoffmann86/team-sprint/ticket"><img src="https://agentmods.dev/badge/skills/leonhoffmann86/team-sprint/ticket.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.00067 | $0.00914 |
| Opus 5 | $0.00034 | $0.00457 |
| Sonnet 5 | $0.00013 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
ticket 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 3d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are turning a rough idea into one well-formed task in TODO.md. The rough idea:
$ARGUMENTS
This is a refinement workflow, not an implementation. Do not write code. Do not write to
TODO.md until the task is crisp and the user has approved it. Work in these steps:
1. Read the constitution
Find the project's constitution files and read them — obey their conventions, especially the risk tiers and any autonomous-agent / TODO-lifecycle rules.
- If
sprint.confexists, read the files listed inSPRINT_CONSTITUTION_FILES(in order). - Otherwise read whichever of
AGENTS.md,CLAUDE.mdexist (and any project-specific guide they reference, e.g. a frontendCLAUDE.md). - Skim
.githooks/README.mdif present, so you describe the downstream effect correctly. If none of these exist, tell the user the repo isn't bootstrapped yet and offer/sprint:bootstrap.
2. Ground the idea in the real code (don't guess)
Find the actual symbols/files the idea touches and its blast radius:
- Code graph (preferred, if available): the
mcp__codegraph__*tools (codegraph_search,…_callers,…_callees,…_impact,…_context), or the CLI (codegraph context "<the idea>",codegraph callers <symbol>,codegraph impact <symbol>); runcodegraph sync .first if the index looks stale. - Fallback (no code graph): use Grep/Glob to locate the relevant symbols and their callers. Read the few files that actually matter. Name concrete functions/files and where the change lands.
3. Interrogate it (the core of this skill)
Challenge the idea against what the code already does. Surface:
- Is it a question or a task? If it's really a question ("…or am I missing something?"), answer it from the code first — existing logic may already cover part of it.
- The real scope and the smallest change that delivers value.
- The risk tier (per the constitution /
AGENTS.md). If high-risk, say so — it will not be auto-implemented; the chain defers it to a human. - The decisions that are the user's to make, not yours (product/UX/policy choices). Ask the user those few decisions with AskUserQuestion. Do not invent answers to genuine product decisions; do correct wrong assumptions using evidence from the codebase.
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.
- 3d ago First seen · 61 lines · 67 tokens per session scan A 8a12c89a5d24
ticket is a skill published in the GitHub repository leonhoffmann86/team-sprint (1 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 914 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.
tasks
Decompose a PLAN / SPEC / FEAT / BUG / DEBT / CHORE into atomic TASK-NNN items ready for the implement flow, via a clean-context subagent. Use when PM mentions "create tasks", "generate TASKs", "break down into tasks", "tasks from PLAN", "break this into tasks", "декомпозиция", "сделай таски", or any request to…
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"…
continue
Autonomous work — find and execute ready tasks.
prd
Create a full Product Requirements Document (PRD-NNN) via a structured PM interview — for large initiatives that justify the overhead. Use when PM mentions "create PRD", "write product requirements", "PRD document", "product brief", "requirements doc", "напиши PRD", "создай PRD", or any request to capture a full…