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/infraspecdev/tesseract/sprint-plangit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/sprint-plan)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/sprint-plan"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/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 | $0.00023 | $0.00212 |
| Opus 5 | $0.00012 | $0.00106 |
| Sonnet 5 | $0.00005 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
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 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
/sprint-plan
Interactive sprint planning workflow.
Steps
- Call
sprint_statusgrouped by epic to see the current state - Show overview: which epics have stories ready, in progress, done
- Ask the user: Which epic/stories to include in the next sprint?
- For selected stories, let the user:
- Assign to team members (show team from config)
- Set priorities (urgent / high / normal / low)
- Set status (e.g. "ready for dev")
- Apply changes via
sprint_bulk_update - Show confirmation table with all changes applied
Notes
- Always show current state before asking for changes
- Validate assignee IDs against the team list in config
- Group changes by type (status, assignee, priority) in the confirmation
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 · 28 lines · 23 tokens per session scan A 9693fe042754
sprint-plan is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 212 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
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.