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/datacore-one/datacoreWrote 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/datacore-one/datacore/sprint-start)<a href="https://agentmods.dev/commands/datacore-one/datacore/sprint-start"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/sprint-start/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/datacore-one/datacore/sprint-start"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/sprint-start.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.00008 | $0.03116 |
| Opus 5.5 | $0.00003 | $0.01246 |
| Sonnet 5.5 | $0.00002 | $0.00623 |
| Haiku 4.5 | $0.00001 | $0.00312 |
Grade A, and why
sprint-start 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 yesterday.
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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Start — Ceremonial Kickoff
Command Context
When to Use
- Monday morning of a new sprint, after Sprint 0 setup is complete
- Or any moment a sprint transitions
planning → active - Pairs with
/sprint-retro(Sprint N close) and/sprint-status(mid-sprint check)
Quick Reference
| Question | Answer |
|---|---|
| Where's the sprint object? | <project>/sprints/<sprint_id>.yaml |
| Where's the canvas? | <project>/CANVAS.md |
| What flips status? | claim.py reading + writing the sprint.yaml status: field |
| What triggers the executor agent? | The sprint-claim cadence in cto.cadences.daily (per the space's venture.yaml) |
| Argument? | <project-path>, e.g. [N]-team/2-projects/product/. Falls back to $DATACORE_SPRINT_PROJECT; ask if neither is set. |
Integration Points
- CANVAS.md — strategic charter (review at ceremony)
- sprint.yaml — sprint object (status flip happens here)
- claim.py — used to seed first claims if humans want to drive an initial pick
- venture cadence_runner — fires
sprint-claimcadence on next heartbeat after status=active - Telegram pilot channel — announce kickoff post-GO
You are the Sprint-Start Facilitator — you run the Monday kickoff ceremony.
Your Role
Lead the team (humans + agents) through the sprint kickoff in five beats:
- Review CANVAS — read it back to ground the sprint in strategy
- Walk the backlog — must / should / stretch with priorities and owners
- Last-minute adjustments — let humans tune the sprint before commit
- GO declaration — flip
sprint.yaml status: planning → active, commit - Launch splash — ceremonial ASCII output, then announce the first move
The ceremony is intentionally a little theatrical. Sprint 1 of a multi-agent project deserves a moment.
Your Workflow
Step 1: Locate the active sprint
Parse $ARGUMENTS for a project path. If absent, use $DATACORE_SPRINT_PROJECT; if that is unset too, ask the user which project.
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.
- yesterday Changed f62a6d79fd25
- 1mo ago First seen · 331 lines · 8 tokens per session scan A b83886b03261
sprint-start is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 3,116 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
voice-refresh
Refresh the founder-voice DNA from new Granola meetings (interactive, MCP-backed). Pulls meetings since the last refresh, harvests Assaf-only speech, runs the Stage 2-3 orchestrator, and presents a founder-gated delta. Never auto-writes voice-dna.md.
decompose
Feature/story breakdown — consume a ready-for-decompose scope doc and produce a task graph in the issue tracker. Re-entrant; tracker-as-canonical with vault breadcrumb.
memory-sprint
Show current sprint state from StudioMeyer Memory.
draft-issue
Draft a GitHub issue based on a discussion or requirements in the current conversation.
close-task
Close the task: update tracking and optionally its GitHub issue.