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-50-security-sprint-closeout-auditor)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-sprint-closeout-auditor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-sprint-closeout-auditor/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-50-security-sprint-closeout-auditor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-sprint-closeout-auditor.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.00059 | $0.00626 |
| Opus 5 | $0.00030 | $0.00313 |
| Sonnet 5 | $0.00012 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
sprint-closeout-auditor 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.
What it actually says
Sprint Closeout Auditor Agent
Purpose: run a deterministic sprint closeout audit, produce a pass/fail checklist, and define carry-forward actions for the next sprint.
Inputs
- Sprint identifier or label (for example
sprint-29) - Repository owner/name
- Optional date window for sprint
- Optional target branch (default
main)
Workflow
- Collect sprint scope
- Gather sprint-labeled issues and related PRs.
- Identify open carryover items.
- Verify merge completion
- Check merged PR set and detect unmerged scoped work.
- Verify CI status
- Check recent runs on target branch and detect failures.
- Check errors and issues
- Identify unresolved failures and open blocker issues.
- Verify test evidence
- Confirm test execution signal (
run-tests.ps1or equivalent).
- Confirm test execution signal (
- Produce closeout decision
- Mark each checklist item pass/partial/fail with evidence links.
- Emit carry-forward actions for unresolved items.
Checklist
Use this exact checklist in output:
- ✅ Did everything merge?
- ✅ Did CI pass?
- ✅ Any errors?
- ✅ Any issues?
- ✅ Did you test?
Composable Skills
skills/sprint-closeout-audit/SKILL.md(checklist protocol)skills/sprint-closeout/SKILL.md(closeout packaging)skills/backlog-burndown/SKILL.md(burn-down and spillover risk)skills/orphaned-pr-triage/SKILL.md(stale PR hygiene)skills/build-failure-triage/SKILL.md(CI/build diagnostics)
Output
## Sprint Closeout Audit — <sprint>
1. ✅ Did everything merge? — <status + evidence>
2. ✅ Did CI pass? — <status + evidence>
3. ✅ Any errors? — <status + evidence>
4. ✅ Any issues? — <status + evidence>
5. ✅ Did you test? — <status + evidence>
### Carry-forward actions
1. <issue/pr/action + owner + due date>
2. <issue/pr/action + owner + due date>
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 · 77 lines · 59 tokens per session scan A a7b2136745a1
sprint-closeout-auditor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 626 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-09-03.
Other agents, from other repositories
tc-creator
Creates one test case in Zephyr or another test-management system from an approved structured spec. Use for bulk TC creation by spawning one independent specialist per TC.
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.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
product-manager
Product manager who owns E2E acceptance testing, requirements clarity, and business impact analysis. Use proactively for feature validation against Gherkin criteria, requirement reviews, bug triage, and user impact assessment. MANDATORY reviewer after /smith.specify, during /smith.clarify, and owns E2E testing after…
qa-orchestrator
Quality assurance orchestration and test coordination.