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 r13v/pi-feature-dev --skill backloggit clone --depth 1 https://github.com/r13v/pi-feature-devWrote 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/r13v/pi-feature-dev/backlog)<a href="https://agentmods.dev/skills/r13v/pi-feature-dev/backlog"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/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/r13v/pi-feature-dev/backlog"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/backlog.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.01526 |
| Opus 5.5 | $0.00032 | $0.00610 |
| Sonnet 5.5 | $0.00016 | $0.00305 |
| Haiku 4.5 | $0.00008 | $0.00153 |
Grade A, and why
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 today.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog
A backlog item is a deferred idea with its reason and evidence. It is an option to return to, not a commitment to do the work. Reading the backlog does not give permission to work an item. Do not commit, push, or post items to a pull request or an issue unless the user asks.
The backlog needs a git repository, because git history keeps the items that were done or dropped. Outside a git repository, tell the user and stop.
Item format
Keep one file for each item: docs/backlog/<slug>.md at the repository root.
The slug names the idea, not a file, such as export-ignores-time-zone.md.
---
worth: later
where: src/export/csv.ts:42
added: 2026-10-23
source: ship 20261023-1500-add-export, f/export @ 01c9a47
---
# Export ignores the time zone of the account
**Idea.** What to change, in one or two sentences.
**Why it matters.** Who gets which result, and what happens without it.
**Evidence.** Places in the code, commands and their output, observations.
**Why it was deferred.** Why the source task did not do it, and what is
still unknown.
worth:yes: the value is agreed. This does not set a schedule.later: the value is not clear yet. The body names the unknown.no: a decision not to do it, with the reason in the body. Keep it so that the same idea is not argued again.
where: optionalpath:line. It is a hint, because lines move.added: the date when the item was added. Do not change it.source: the task that found the idea, the branch, and the short commit.
Write the body for a reader who does not know the source task.
A file that exists is an open item. When the idea is done, delete the file in the change that does it. When the idea is dropped, delete the file. Do not add a status field, an archive, or an index file.
An item is stale when the claim in its evidence is no longer true in the
current code. A moved line does not make an item stale. Update its where.
Change an existing item only to add evidence, to update where, to change
worth, or to delete it. Do not rewrite other text in it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +6 lines d74f775d32e3
- 9d ago First seen · 138 lines · 79 tokens per session scan A 2778dd118a9f
backlog is a skill published in the GitHub repository r13v/pi-feature-dev (3 stars, last pushed 2d ago), licensed MIT. It adds 79 tokens to every session and 1,526 once invoked, about $0.0003 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-10-24.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…