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/leifericf/agentic-sdk/create-backlognpx skills add leifericf/agentic-sdk --skill create-backloggit clone --depth 1 https://github.com/leifericf/agentic-sdkWhat 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.00012 | $0.00411 |
| Opus 5 | $0.00006 | $0.00205 |
| Sonnet 5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
create-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 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
create-backlog
Translate the technical design into a prioritized, living product backlog of capabilities. No implementation task breakdown.
Procedure
- Read
project-meta.md,problem-description.md,product-requirements.md,risk-assumption-review.md,technical-design.md,decision-log.md, andopen-questions.md(ux-design-guide.mdoptional). If a required prerequisite is missing, returnblocked: <which artifact>. - Surface and resolve
[Blocking]items affectingproduct-backlog.md. - Draft a simple capability hierarchy from the artifacts; iterate with the user to confirm priority, sequencing, and scope, at most three questions per turn. Check for missing capabilities and validate priority assumptions.
- If blocked by missing information, add a
[Blocking]item toopen-questions.mdand stop. If new decisions are needed, record them indecision-log.mdfirst. - Write
~/.agentic-sdk/<project>/artifacts/planning/product-backlog.mdas one living document with exactly these buckets in order:Now / Next,Later,Inbox (untriaged),In product (shipped). No IDs; priority is order within the bucket; each item appears once in one bucket; child items indent two spaces under their parent; no prose around the list.In product (shipped)holds plain capability names only, no dates or versions.
Boundaries
Owns the prioritized capability backlog. pick-feature owns selecting and triaging the next item; plan-feature owns decomposing one item into a plan. Reached by plan-system.
Return
One line: the artifact written and a terse status, or blocked: <reason>.
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 · 41 lines · 12 tokens per session scan A 1ff800d5d42d
create-backlog is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 13d ago), licensed MIT. It adds 12 tokens to every session and 411 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-08-31.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
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.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
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.
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.