agentmods.dev

sprint-sync

A command that compares planning documents with the matching tasks in ClickUp and shows what differs. It can then create, update, or link tasks after you choose what to apply.

In plain words
What is it for?
Use it to check an epic or all epics, review missing or changed stories, and apply selected task changes in bulk.
Why use it?
It prevents planning documents and ClickUp from drifting apart, while showing proposed changes before anything is modified.

Command

5 2mo ago A scan 22 tokens original MIT
View the source file infraspecdev/tesseract
Install

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.

agentmods
npx agentmods add commands/infraspecdev/tesseract/sprint-sync
Clone the repo
git clone --depth 1 https://github.com/infraspecdev/tesseract
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 498 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00498
Opus 5 $0.00011 $0.00249
Sonnet 5 $0.00004 $0.00100
Haiku 4.5 $0.00002 $0.00050

Measured 2d ago against content hash 344fe26a7181, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

clickup-sprint-planner/commands/sprint-sync.md · 49 lines

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

  1. Load sprint-planner.json config
  2. Call sprint_sync for the specified epic (or all epics if none given)
  3. 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   │
└──────────┴─────────────────────────────────────────┴──────────┘
  1. Ask the user: apply all / pick which / cancel
  2. For "to_create" stories: call sprint_bulk_create with set_relationships: true
  3. For "to_update" stories: call sprint_bulk_update with the relevant changes
  4. 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
  5. Show results + any failures
  6. 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
Changes

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.

  1. 2d ago First seen · 49 lines · 22 tokens per session scan A 344fe26a7181

Subscribe to this mod's changes

sprint-sync is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 498 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.

Code reviewPlanningProject management
Related

Other commands, from other repositories

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

project-recap

Generate a visual project recap for context switching.

nicobailon/visual-explainer · 12 tokens

speckit.taskstoissues

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

VisActor/VChart · 21 tokens

ado-pull

Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.

anton-abyzov/specweave · 23 tokens

issue-amend

Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.

assafkip/kipi-system · 26 tokens

dispatch-worker

Run one in-session-agent Worker tick (RFC-0041 §4.3.1).

ai-sdlc-framework/ai-sdlc · 191 tokens