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-project-mapper)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-sprint-project-mapper"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-sprint-project-mapper.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.00080 | $0.00639 |
| Opus 5 | $0.00040 | $0.00319 |
| Sonnet 5 | $0.00016 | $0.00128 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
sprint-project-mapper 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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint/Project Mapper Agent
Purpose: transform fragmented issues/PRs into coherent, statistically meaningful sprint or project groups, then generate metrics and release-note summaries that stakeholders can trust.
Inputs
- Repository (
owner/repo) and optional milestone/sprint window - Source objects: issues, PRs, branches, labels, timestamps
- Grouping hints (optional):
sprint:*,wave:*,project:*,area/*,epic/* - Minimum significance thresholds (defaults provided below)
Workflow
Phases 1-4 — Collect, Group, Debate, Gate
See agents/references/sprint-project-mapper-detail.md for the
full collect/normalize, candidate grouping, split-vs-merge debate, and significance-gate workflow.
Phase 5 — Metrics
Compute per finalized group:
- issue count (open/closed)
- PR count (opened/merged)
- total LOC changed
- median cycle time
- P95 cycle time
- closure ratio (closed / total)
- duplicate/invalid ratio
- blocker count
- lead contributors (top PR authors by merged PR count)
Phase 6 — Outputs
Produce:
- Group map table (
Group,Criteria,Issue Count,PR Count,LOC,Cycle Time) - Debate log (
Group,Split Argument,Merge Argument,Decision,Confidence) - Release-note-ready bullets per meaningful group
- Outlier report (small/noisy groups excluded from primary metrics)
Output Format
## Sprint/Project Mapping Report — <repo> — <date>
### Final Groups
| Group | Basis | Issues | PRs | LOC | Median Cycle Time |
|------|-------|-------:|----:|----:|------------------:|
### Debate Decisions
| Group | Decision | Confidence | Rationale |
|------|----------|-----------:|-----------|
### Release Notes (Proposed)
- **<Group>**: <impact summary with linked issues/PRs>
### Excluded/Residual Items
- <reason + issue/PR list>
Non-Goals
- Do not edit code.
- Do not auto-close issues or rewrite sprint boards.
- Do not fabricate links where no evidence exists in GitHub metadata.
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.
- 4d ago Changed · -43 lines · +80 tokens per session e70a1d50e992
- 8d ago First seen · 125 lines · 0 tokens per session scan A 1190e263f1b7
sprint-project-mapper is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 639 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…