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 mpazik/Binder --skill refine-backloggit clone --depth 1 https://github.com/mpazik/BinderWrote 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/mpazik/binder/refine-backlog)<a href="https://agentmods.dev/skills/mpazik/binder/refine-backlog"><img src="https://agentmods.dev/badge/skills/mpazik/binder/refine-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/mpazik/binder/refine-backlog"><img src="https://agentmods.dev/badge/skills/mpazik/binder/refine-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01291 |
| Opus 5.5 | $0.00012 | $0.00516 |
| Sonnet 5.5 | $0.00006 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
refine-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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refine draft tasks to meet the Definition of Ready so they can move from draft to pending.
$ARGUMENTS
If specific tasks were given above, focus on those. Otherwise, work through the draft tasks listed below.
Draft Tasks
!binder search type=Task status=draft -f "key,title,taskType,priority,size,partOf" --format tsv
If no drafts are listed above, tell the user there's nothing to refine and stop.
Refinement Steps
For each task, work through these steps. Use binder read <key> --format yaml to inspect full details first.
Draft tasks from capture may already have fields set. Respect what's there -- only fill gaps unless user said otherwise.
1. Duplicate Check
- Compare against existing tasks, features, and concepts in Context below
- Also check cancelled tasks — don't recreate something deliberately cancelled
- If overlap found:
- Exact duplicate → cancel the draft, link to the existing one
- Partial overlap → merge the unique parts into the existing task, cancel the draft
- Related but distinct → keep both, link with
relatesTo
2. Classify
- Set
taskTypeif missing — match to the closest category (fix, feat, tweak, refactor, perf, agent, build, docs, test) - Set
sizeif missing — small: few files, no design decisions. medium: several files, 1-2 decisions. large: multiple commits, non-trivial decisions required. - Set
priorityif missing — p0=Blocker, p1=Urgent, p2=High, p3=Medium (default), p4=Low - Set
moduleif missing — which part of the codebase this belongs to - Set
sourceFilesif relevant files are obvious from the description
3. Describe
- Improve
titleif unclear (2-7 words, no verb prefix, max 70 chars) - Write
descriptionif missing (1-2 sentences with enough context)
4. Definition of Ready
Required for all tasks: title, taskType, size, priority, module, description.
Additional by size:
- medium+ tasks: add
constraints - large tasks: add
outOfScope
Additional by type:
- feat tasks: add
acceptanceCriteriawith testable scenarios - fix tasks: add
acceptanceCriteria(how to verify the fix) - refactor tasks: add
constraintsstating what behavior must not change
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 First seen · 130 lines · 29 tokens per session scan A c898aefee993
refine-backlog is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 28d ago), licensed MIT. It adds 29 tokens to every session and 1,291 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-30.
Other skills, from other repositories
kanban-tasks
A task-board workflow for breaking work into cards and moving them through stages such as inbox, ready, doing, review, and done. It also includes a background service and a web interface for the board.
pad
Work with the user's Pad workspaces through the Pad tools. Find, read, create and update tasks, bugs, ideas, plans and docs; comment on them, link them, and see what to work on next. Use it whenever the user talks about their Pad projects or items.
forward-plan
Use when turning Brigade's native ready set, outcome rank, and ROADMAP.md into a dependency-filed plan artifact under .brigade/work/plans/ - propose GraphTrail-derived edges (blocks from def/use, conflicts-with from write overlap) marked derived and requiring confirmation. Degrade cleanly when GraphTrail is…
graft
Persistent graph memory shared across conversations and agents. Graft is a prompter, not a cache: it hands you notes that may be close to the problem in front of you, and a close note is already a win - it gives you a starting point and reminds you what was decided before. Search it before non-trivial work, and write…
handoff-inbox-drain
Use when draining a Brigade handoff review inbox - triage drafts with allowlist-bound Brigade handoff commands, grounded edits that cite on-disk content, archive-only retention, and reinforce-in-place when ingest already matched a known fact (#724). Never delete, remove, or prune.
memory-audit
Maintenance pass + health check of the graft graph. Runs the graft maintain loop: checks what is due, applies the mechanical cleanup, then adjudicates every maintenance candidate (near duplicates, supersessions, contradictions, memories whose source file changed or disappeared, keyword variants, stale low-value notes)…