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-sync)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/sprint-sync"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/sprint-sync/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-sync"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/sprint-sync.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.00022 | $0.00498 |
| Opus 5.5 | $0.00009 | $0.00199 |
| Sonnet 5.5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
sprint-sync 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-sync [epic]
Sync plan documents against ClickUp, then optionally apply changes.
IMPORTANT: Never use raw ClickUp MCP tools (clickup_create_task, clickup_update_task, etc.) for sprint operations. Always use the sprint_* tools which handle action logging, naming conventions, and relationship linking automatically.
Steps
- Load
sprint-planner.jsonconfig - Call
sprint_syncfor the specified epic (or all epics if none given) - Present the diff as a table:
┌──────────┬─────────────────────────────────────────┬──────────┐
│ Status │ Story │ Action │
├──────────┼─────────────────────────────────────────┼──────────┤
│ ✅ match │ S1: Create new ECS infrastructure │ none │
│ ⚠️ diff │ S3: Create new ALB — name diverged │ update │
│ 🔗 link │ S4: Set up monitoring — unlinked task │ link │
│ 🆕 new │ S6: Configure CloudWatch alarms │ create │
└──────────┴─────────────────────────────────────────┴──────────┘
- Ask the user: apply all / pick which / cancel
- For "to_create" stories: call
sprint_bulk_createwithset_relationships: true - For "to_update" stories: call
sprint_bulk_updatewith the relevant changes - For "to_link" stories (unlinked tasks matched by fuzzy name):
- Show candidates with match confidence
- If user approves: call
sprint_sync(apply_links=true)to auto-set relationship fields
- Show results + any failures
- Offer to write ClickUp IDs back into the plan document
Arguments
epic(optional): Epic ID like "P1a", "P2", "P3". Omit for all epics.
Examples
/sprint-sync P1a # Sync epic P1a only
/sprint-sync # Sync all epics
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 · 49 lines · 22 tokens per session scan A 344fe26a7181
sprint-sync is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 498 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.