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.
git 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-status)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/sprint-status"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/sprint-status/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/commands/infraspecdev/tesseract/sprint-status"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/sprint-status.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.00019 | $0.00396 |
| Opus 5.5 | $0.00008 | $0.00158 |
| Sonnet 5.5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
sprint-status 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 1mo 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-status [epic] [--by status|assignee]
Show sprint status from ClickUp.
Steps
- Call
sprint_statuswith the requested grouping - Render summary table:
Epic │ Total │ Done │ In Progress │ Ready │ Blocked
───────┼───────┼──────┼─────────────┼───────┼────────
P1 │ 12 │ 8 │ 2 │ 2 │ 0
P1a │ 5 │ 0 │ 2 │ 3 │ 0
P2 │ 8 │ 0 │ 0 │ 8 │ 0
- If a specific epic was requested, also show story-level detail:
# P1a: ECS VPC Migration (2/5 in progress)
│ Status │ Story │ Assignee │
│ 🔵 in progress│ S1: Create new Launch Template │ Alice │
│ 🔵 in progress│ S2: Create new ALB │ Bob │
│ ⚪ ready │ S3: Migrate ECS services │ — │
Arguments
epic(optional): Epic ID like "P1a" for detailed view--by status: Group by status instead of epic--by assignee: Group by assignee instead of epic
Examples
/sprint-status # Overview of all epics
/sprint-status P1a # Detailed view of epic P1a
/sprint-status --by assignee # Group all tasks by assignee
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.
- 1mo ago First seen · 48 lines · 19 tokens per session scan A f1c5aae2cd46
sprint-status is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 396 once invoked, about $0.0001 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.