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 commands/parkerm2/create-claude-workflow/sprint-ticketsgit clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWrote 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/commands/parkerm2/create-claude-workflow/sprint-tickets)<a href="https://agentmods.dev/commands/parkerm2/create-claude-workflow/sprint-tickets"><img src="https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/sprint-tickets.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.00023 | $0.04343 |
| Opus 5 | $0.00012 | $0.02171 |
| Sonnet 5 | $0.00005 | $0.00869 |
| Haiku 4.5 | $0.00002 | $0.00434 |
Grade A, and why
sprint-tickets 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 6d 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Tickets Command
This command displays your current sprint in a clean, scannable format with complete ticket details, sprint health metrics, and filtering options.
Usage
/sprint-tickets # Full sprint view
/sprint-tickets --assignee me # Your assigned tickets
/sprint-tickets --status "In Progress" # Specific status
/sprint-tickets --label "bug" # By label
/sprint-tickets --priority high # By priority
/sprint-tickets --group assignee # Group by assignee instead of status
/sprint-tickets --format detailed # Show full descriptions
Arguments
--assignee <name|me>- Filter by assignee (use "me" for current user)--status <status>- Filter by status (To Do, In Progress, In Review, Done, etc.)--label <label>- Filter by label--priority <priority>- Filter by priority (Highest, High, Medium, Low, Lowest)--group <by>- Group by: status (default), assignee, priority, label--format <format>- Output format: compact (default), detailed--board <board-id>- Override stored board ID (for multi-board projects)--include-archived- Include archived/closed sprints (use with caution)
First Run: Auto-Detection
On first run, the command will:
- Fetch all agile boards accessible to the user
- If only one board exists, use it automatically
- If multiple boards exist, prompt user to select
- Store board ID and project key in memory for future sessions
- Auto-detect the currently active sprint
To reset stored board preference: /sprint-tickets --reset-board
Output Format
Sprint Overview Header
╔════════════════════════════════════════════════════════════════════╗
║ SPRINT: Sprint 24 "Q1 Core Features" ║
║ Goal: Improve dashboard performance and add bulk operations ║
║ Dates: 2026-03-24 → 2026-04-07 (15 days) ║
║ Status: 12 days remaining • 47% complete (47/100 points) ║
╠════════════════════════════════════════════════════════════════════╣
║ Velocity: 100 pts/sprint | Capacity: 120 hrs | Team: 4 members ║
║ Burndown: ▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╚════════════════════════════════════════════════════════════════════╝
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.
- 6d ago First seen · 472 lines · 23 tokens per session scan A 1121557c4b95
sprint-tickets is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 4,343 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.