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.00423 |
| Opus 5.5 | $0.00010 | $0.00169 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
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 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
Mission
Organize, triage, and prioritize unfulfilled requirements, technical debt, and prospective features, ensuring no ideas or defect signals are lost during long-term development.
Inputs and Outputs
- Read
.agents/memory/constitution.md, existing backlog files (.agents/backlog/IDEAS.md,TECHNICAL_DEBT.md), recent specs, and codebase search results. - Preserve stable item IDs, maintain prioritization rationale, and record dated state transitions when promoting or resolving items.
Protocol
1. Intake & Deduplication
- Capture problem statement, user value, reproducibility evidence, affected component, priority, and clear acceptance criteria.
- Deduplicate against existing items by linking related IDs; categorize as Feature Idea, Bug, Technical Debt, or Security Risk. Never silently discard an item.
2. Automated Debt & Marker Scan
- Scan targeted scope for source markers (
TODO:,FIXME:,HACK:,BUG:) usingrg; record file, line number, actionable context, and severity. - Persist scanned debt findings in
.agents/backlog/TECHNICAL_DEBT.mdwith timestamp and query command.
3. Grooming & Promotion
- Periodically review stale or blocked backlog items, establish minimal next actionable steps, and promote ready items to formal feature specs (
spec.md). - Ensure priority changes have explicit rationale; never close or mark items resolved without verified test or acceptance evidence.
Completion Gate
Backlog entries are categorized with stable IDs, technical debt logs reflect current codebase reality, and promoted items link to corresponding specifications.
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.
- DO NOT mark items resolved without verified test, review, or user acceptance evidence.
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 Changed · +9 lines df2222797f6d
- 2mo 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 (3 stars, last pushed 17d ago), licensed MIT. It adds 25 tokens to every session and 423 once invoked, about $0.0001 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-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
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
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.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
stakeholder-update
Drafts a weekly update, executive summary, escalation, or launch announcement for readers outside the working group. Use when preparing status or launch communication for leadership, partners, or customers.