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 wedabro/bro-skills --skill speckit.backloggit clone --depth 1 https://github.com/wedabro/bro-skillsWrote 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/wedabro/bro-skills/speckit.backlog)<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.backlog"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.backlog/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/wedabro/bro-skills/speckit.backlog"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.backlog.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.00025 | $0.00266 |
| Opus 5 | $0.00013 | $0.00133 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
speckit.backlog 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 9d 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
🎯 Mission
Organize and prioritize unfulfilled requirements, ensuring no ideas or bugs are missed during long-term development.
📋 Protocol
Phase 1: Idea Scoping (Idea recording)
- When a user makes a request that they don't want to do right away, save it to
.agents/backlog/IDEAS.md. - Each idea needs: Description, Priority (Low/Med/High), Status (Pending).
Phase 2: Automated Todo Scan (Scan source code)
- Use the command
grepto find the keywords:TODO:,FIXME:,HACK:,BUG:. - Summarize the results found into
.agents/backlog/TECHNICAL_DEBT.md.
Phase 3: Backlog Grooming (Backlog filtering)
- Periodically review items in the backlog to convert to
spec.mdwhen the user is ready to deploy.
🚫 Guard Rails
- DO NOT arbitrarily delete the backlog without asking the user.
- DO NOT overflow the context by listing thousands of TODOs. Only list tasks related to the area you are working on.
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.
- 9d ago First seen · 25 lines · 25 tokens per session scan A cff375a3113e
speckit.backlog is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 25 tokens to every session and 266 once invoked, about $0.0001 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 skills, from other repositories
working-days-get-working-days
Calculate the number of working days between two dates, optionally accounting for country-specific holidays.
pm-karpathy-thinking
Stress-test a product decision, PRD, roadmap, experiment, or feature proposal using explicit assumptions, simplicity-first scope, surgical changes, and measurable verification loops. Use when product work is ambiguous, over-scoped, solution-led, risky, or needs a clear go/no-go recommendation.
pm-vietnamese-copilot
Create decision-ready, delivery-ready bilingual Vietnamese-English product management artifacts. Use for discovery, PRDs, user stories, prioritization, roadmaps, OKRs, metrics, experiment plans, feedback analysis, meeting synthesis, stakeholder updates, and pre-mortems.
pm-bilingual-copilot
Create concise bilingual Vietnamese-English product management artifacts and translate PM context accurately across both languages. Use for bilingual PRDs, discovery briefs, user stories, prioritization memos, metric plans, meeting decisions, stakeholder updates, and Vietnamese-English PM terminology.
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
plan
Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.