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 mazen160/backlog --skill backlog-enhance-tasksgit clone --depth 1 https://github.com/mazen160/backlogWrote 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/mazen160/backlog/backlog-enhance-tasks)<a href="https://agentmods.dev/skills/mazen160/backlog/backlog-enhance-tasks"><img src="https://agentmods.dev/badge/skills/mazen160/backlog/backlog-enhance-tasks.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.1 | $0.00050 | $0.00741 |
| Opus 5 | $0.00025 | $0.00370 |
| Sonnet 5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
backlog-enhance-tasks 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backlog-enhance-tasks
Enhance a backlog task's title, description, and optionally generate a plan using Claude.
When to use
Invoke as /backlog-enhance-tasks TASK-N or /backlog-enhance-tasks TASK-N --build-plan.
Accepts: a task ref (TASK-N or bare integer), optional --build-plan flag.
Workflow
1. Fetch the task
./backlog --profile default task show <ref> --json
Parse the JSON. Extract: id, seq, title, description, type, priority, project.
2. Rewrite the title
Improve the title for clarity and specificity. Rules:
- Use imperative verb ("Add", "Fix", "Remove", "Expose", "Migrate" — not "Adding" or "Added")
- Be specific: include the subsystem or file if known (e.g., "Fix circular onclick rebind in load-more button" not "Fix button bug")
- Keep it under 80 chars
- Do not change the intent or scope
3. Expand the description
Rewrite the description as structured markdown with these sections (omit sections that don't apply):
## Context
<1-2 sentences on why this matters — what breaks or is missing without it>
## Acceptance criteria
- [ ] <specific, testable criterion>
- [ ] <specific, testable criterion>
- [ ] ...
## Implementation hints
<optional: file paths, function names, API patterns — only if clearly known>
Rules:
- Keep what's already correct in the existing description
- Do not invent scope that isn't implied by the title/type/context
- Write for a developer who hasn't seen this codebase before
4. Write back to the task
./backlog --profile default task update <ref> \
--title "<improved title>" \
--description "<expanded description>" \
--as "ai:claude-sonnet-4-6"
5. Build plan (if --build-plan flag provided)
Generate a concise implementation plan:
## Steps
1. <first concrete action — file, function, what to change>
2. <next action>
...
## Testing
- <how to verify this works>
Then attach it:
./backlog --profile default plan add \
--task <ref> \
--title "Implementation plan" \
--content "<plan markdown>" \
--as "ai:claude-sonnet-4-6"
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.
- 8d ago First seen · 105 lines · 50 tokens per session scan A 5ef46fea7624
backlog-enhance-tasks is a skill published in the GitHub repository mazen160/backlog (15 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 741 once invoked, about $0.0003 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-30.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
stakeholder-alignment
Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
brainstorming
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.