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.
npx skills add ivegamsft/basecoat --skill backlog-burndowngit 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/skills/ivegamsft/basecoat/backlog-burndown)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/backlog-burndown"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/backlog-burndown/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/skills/ivegamsft/basecoat/backlog-burndown"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/backlog-burndown.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.00086 | $0.00360 |
| Opus 5.5 | $0.00034 | $0.00144 |
| Sonnet 5.5 | $0.00017 | $0.00072 |
| Haiku 4.5 | $0.00009 | $0.00036 |
Grade A, and why
backlog-burndown 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 1mo 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
Backlog Burndown Skill
Use this skill when you need a structured way to track backlog completion pace, scope drift, and risk to sprint commitments.
Use Cases
- Daily burn-down check for sprint backlog health.
- Mid-sprint risk review for scope creep and blocked work.
- End-of-week status update with actionable backlog triage recommendations.
- Combined issue-and-open-PR burn-down so in-flight PRs count toward remaining scope.
Reference Files
| File | Purpose |
|---|---|
references/burndown-workflow.md |
Step-by-step workflow and report format |
references/metrics-formulas.md |
Formulas for burn-down, spillover, and blocker pressure |
Agent Pairing
sprint-plannerfor commitment and capacity context.issue-triagefor blocker and priority updates.orphaned-pr-cleanupfor open-PR state, mergeability, and stale-PR triage.product-managerfor scope trade-off decisions.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 37 lines · 86 tokens per session scan A 0f6d42f51aa5
backlog-burndown is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 10d ago), licensed MIT. It adds 86 tokens to every session and 360 once invoked, about $0.0003 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 skills, from other repositories
360-feedback-system
360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
announcement-board
Announcement board: author, category, department, priority, audience, publish and expiry dates, status and acknowledgements, as CSV, SQL, JSON Schema or Notion on request. Use for internal notices.
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
brace-escalate
Design escalation path -- Tier 1 to Tier 2 to Engineering handoff, decision criteria, and communication templates. Use when asked to "design our escalation process", "when should support escalate to engineering", "build an escalation runbook", or "reduce escalation rate".
brace-recon
Support operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a…