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 agentmods add skills/sienklogic/plan-build-run/backlognpx skills add SienkLogic/plan-build-run --skill backloggit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/backlog)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/backlog"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/backlog.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 | $0.00023 | $0.00538 |
| Opus 5 | $0.00012 | $0.00269 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
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 today.
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
STOP — DO NOT READ THIS FILE. You are already reading it.
/pbr:backlog — Backlog Parking Lot
Manage ideas that aren't ready for active planning. Backlog items use 999.x numbering to stay outside the active phase sequence. They can be promoted to active phases when ready.
Step 0 — Banner
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► BACKLOG ║
╚══════════════════════════════════════════════════════════════╝
Subcommands
/pbr:backlog add <description>
- Create
.planning/phases/directory if needed - Find next 999.x number: scan for existing
999.*dirs, increment - Generate slug from description
- Create
.planning/phases/999.{x}-{slug}/ - Write a minimal PLAN.md with just the description as objective (no tasks — this is a placeholder)
- Display:
Backlog item 999.{x}: {description}
/pbr:backlog review
- Scan
.planning/phases/999.*directories - If none found: display "No backlog items." and exit
- For each item, read its PLAN.md objective
- Display all items in a numbered list
- Use AskUserQuestion for each item:
- Promote — Move to active milestone (renumber into current sequence)
- Keep — Leave in backlog
- Remove — Delete the directory
/pbr:backlog promote <N>
- Find the 999.{N} directory
- Determine next active phase number (highest non-999 phase + 1)
- Rename directory from
999.{N}-{slug}to{next}-{slug} - Update ROADMAP.md to include the new phase
- Display:
Promoted backlog item to Phase {next}: {slug}
Anti-Patterns
- DO NOT create backlog items for work that should be a todo — backlog is for phase-level ideas
- DO NOT auto-promote items — always require user decision
- DO NOT renumber existing active phases when promoting
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.
- today First seen · 57 lines · 23 tokens per session scan A aa76437f529f
backlog is a skill published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 538 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-09-03.
Other skills, from other repositories
doncheli-planning
Run weekly team planning with RFC review, WSJF prioritization and assignment by person/pair/squad with capacity calculation. Activate when user mentions "planning", "sprint", "weekly planning", "RFC", "team planning", "prioritize backlog", "WSJF".
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
lane-contract
File-based task contracts under .agents/runs/ with ownspaths, verification tiers L0/L1/L2, and solo merge rules. Use when user says info, справка, lane-stack:lane-contract info, or when authoring or reviewing task YAML, ownspaths, acceptance, or verification commands.
resume-project
Cold-start project context for orchestrator or human. Use when user says info, справка, lane-stack:resume-project info, resume, продолж, where were we, cold start, or starting a new orchestrator session on an existing repo.
doncheli-api-contract
Design complete API contracts covering endpoints, auth, rate limiting, error handling, retries, circuit breaker and idempotency. Activate when user mentions "api contract", "api design", "endpoint", "webhook", "REST", "GraphQL", "OpenAPI", "design the API".
doncheli-debate
Run an adversarial multi-role debate to surface trade-offs and reach a reasoned decision. Activate when user mentions "debate", "discuss", "trade-off", "decision", "compare options", "pros and cons", "choose between".