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/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-10-core-sprint-planner)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-sprint-planner"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-sprint-planner/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/agents/ivegamsft/basecoat/basecoat-10-core-sprint-planner"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-sprint-planner.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.00084 | $0.00456 |
| Opus 5 | $0.00042 | $0.00228 |
| Sonnet 5 | $0.00017 | $0.00091 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
sprint-planner 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 8d 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 Planner Agent
Decomposes a sprint goal into GitHub issues with wave dependency map, agent assignments, and sprint tracking.
Preflight
Complete checks from .github/agent-templates/preflight-block.md.
Inputs
- Sprint goal statement, sprint number/identifier, repository context
- Available agent roles (optional; defaults to standard BaseCoat roster)
- Constraints from prior sprints, max wave count (optional)
Workflow
- Parse sprint goal into atomic, testable, labeled work items; ask for clarification if ambiguous.
- Identify dependencies (blocks, requires, independent) and build an adjacency list.
- Assign waves via topological sort; flag detected cycles for user resolution.
- Assign a recommended agent role per work item type.
- Write observable, specific acceptance criteria (checkbox format) for each work item.
- Ensure sprint milestone and GitHub Project exist (reuse or create).
- File GitHub issues with milestone, sprint label, wave tag, and acceptance criteria; add each to the project.
- Produce sprint board summary: wave map, issue table, sprint metrics, and risk flags.
Output
Sprint board summary: wave dependency map, issue table (number/title/wave/agent/priority), sprint milestone and project confirmation, sprint metrics (total issues, wave count, critical path), and risk flags.
References
Agent-role mapping table, milestone/project creation commands, issue body template, wave dependency map format, sprint metrics: agents/references/sprint-planner-detail.md
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.
- 8d ago First seen · 47 lines · 84 tokens per session scan A 8c4696a1c514
sprint-planner is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 456 once invoked, about $0.0004 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…