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/infraspecdev/tesseract/sprint-planningnpx skills add infraspecdev/tesseract --skill sprint-planninggit 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/skills/infraspecdev/tesseract/sprint-planning)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/sprint-planning"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/sprint-planning.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.00052 | $0.01164 |
| Opus 5 | $0.00026 | $0.00582 |
| Sonnet 5 | $0.00010 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
sprint-planning 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planning Skill
Overview
Orchestrate ClickUp sprint operations through the sprint-planner MCP server — sync plan documents, create story cards in bulk, and track sprint progress.
Core principle: Always sync before mutating. Show the user the diff, get confirmation, then execute.
When to Use
- Syncing plan docs to ClickUp (creating/updating stories)
- Bulk operations on ClickUp tasks (create, update, reorder)
- Sprint status checks and epic progress tracking
- Setting EPIC relationship fields on tasks
When NOT to Use
- Individual task updates — use ClickUp UI directly
- Creating plan documents — use
dev-workflow:plan-docsskill - Non-ClickUp project management
Available Tools
| Tool | Purpose |
|---|---|
sprint_sync |
Diff plan docs against ClickUp state (read-only) |
sprint_bulk_create |
Create multiple tasks + set EPIC relationships |
sprint_set_relationship |
Set list_relationship custom fields directly |
sprint_bulk_update |
Batch update status/assignee/priority |
sprint_bulk_rename |
Preview/apply [EpicID] prefix to non-compliant task names |
sprint_status |
Get epic overview with stats |
sprint_action_log |
Query past operations |
Rules
- Sync before mutating. Always call
sprint_syncfirst. Present the diff and get confirmation. - Use bulk operations. Never create tasks one-by-one. Use
sprint_bulk_createwithset_relationships: true. - Read config, don't hardcode. All IDs come from
sprint-planner.json(path viaSPRINT_PLANNER_CONFIGenv var). Never hardcode ClickUp IDs. - Confirm before mutating. Show the user exactly what will happen and ask for confirmation.
- Surface errors clearly. Our tools use the direct REST endpoint — if they report failure, it's real. Show which operations succeeded vs failed.
- Present results as tables. After any operation, show task names, IDs, statuses, and any failures.
- Never use raw ClickUp MCP tools for sprint write operations. Tools like
clickup_create_task,clickup_update_task,clickup_create_task_commentbypass the action log, skip relationship linking, and ignore naming conventions. Always usesprint_bulk_create,sprint_bulk_update, andsprint_set_relationshipinstead.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 102 lines · 52 tokens per session scan A ed1eb055dd60
sprint-planning is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,164 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…