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/implementnpx skills add backloghq/backlog --skill implementgit 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.00050 | $0.00425 |
| Opus 5 | $0.00025 | $0.00212 |
| Sonnet 5 | $0.00010 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
implement 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 yesterday.
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
Implement Task
Pick up a task and implement it. If an argument is provided, use it as the task ID. Otherwise, pick the highest-urgency unblocked task.
Process
-
Find the task — if "$ARGUMENTS" is provided, ALWAYS resolve it with
task_infofirst to confirm the task exists and get its current state (status, project, deps, attached doc). Otherwise, calltask_listwith filterstatus:pendingand pick the highest-urgency task that is NOT blocked (+BLOCKED). Use the UUID from this lookup for every subsequenttask_start/task_done/task_annotatecall — never substitute a UUID from memory or a previous unrelated context. -
Read the spec — call
task_doc_readto check if the task has an attached spec. If it does, read it carefully — it defines what to build and how to verify. -
Start the task — call
task_startto mark it as actively being worked on. -
Do the work — implement what the task and spec describe. Write code, create files, run tests. Use the codebase tools (Read, Edit, Write, Bash, Grep, Glob) as needed.
-
Verify — check the acceptance criteria from the spec. Run relevant tests. Make sure the implementation is complete.
-
Complete the task — call
task_doneto mark it as completed. Add an annotation withtask_annotatesummarizing what was done if the changes aren't obvious. -
Check what's next — call
task_listwith filterstatus:pendingto see if completing this task unblocked anything. Mention what's ready to pick up next.
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.
- yesterday First seen · 25 lines · 50 tokens per session scan A 63173b5f796f
implement is a skill published in the GitHub repository backloghq/backlog (5 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 425 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-31.
Other skills, from other repositories
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.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.