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/backloghq/backlog/plannpx skills add backloghq/backlog --skill plangit clone --depth 1 https://github.com/backloghq/backlogWhat 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.00038 | $0.00412 |
| Opus 5 | $0.00019 | $0.00206 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
plan 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 2d 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
Plan Work
Break down the given goal into actionable tasks. The goal is: "$ARGUMENTS"
Process
-
Understand the goal — analyze what "$ARGUMENTS" requires. Read relevant code, configs, and docs in the codebase to understand the current state.
-
Decompose into tasks — create a logical breakdown of work items. Each task should be:
- Small enough to complete in one focused session
- Clear about what "done" looks like
- Independent where possible, with explicit dependencies where not
-
Create tasks — for each task, use
task_addwith:- A clear, actionable description (start with a verb, max 500 chars — keep it to a one-line summary; longer content goes in step 4)
projectset to a logical groupingprioritybased on urgency and importance (H for blockers, M for core work, L for nice-to-have)tagsfor categorization (e.g.,frontend,backend,testing,docs)dependsto express ordering constraints (use UUIDs from previously created tasks)scheduledif the task shouldn't start until a certain date
-
Write specs for complex tasks — for any task that needs detailed requirements or context (anything that wouldn't fit in 500 chars), use
task_doc_writeto attach a markdown document explaining:- What needs to be built
- Key technical decisions
- Acceptance criteria
- Relevant code locations
-
Present the plan — show the created tasks in dependency order with their IDs, descriptions, and priorities. Highlight the first task(s) that can be started immediately (not blocked).
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.
- 2d ago First seen · 34 lines · 38 tokens per session scan A b538ba6d95c7
plan is a skill published in the GitHub repository backloghq/backlog (5 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 412 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.