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/mazen160/backlog/backlog-loopnpx skills add mazen160/backlog --skill backlog-loopgit clone --depth 1 https://github.com/mazen160/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.00133 | $0.05687 |
| Opus 5 | $0.00067 | $0.02844 |
| Sonnet 5 | $0.00027 | $0.01137 |
| Haiku 4.5 | $0.00013 | $0.00569 |
Grade A, and why
backlog-loop 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.
How it starts
The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backlog-loop
One task in. Iterate until a skeptical Judge says it's actually done. Exit.
The name is a callback to the Ralph loop: the loop is on a single task — implement → verify → judge → fix → re-judge — bounded by a max iteration count. This skill never picks up a second task.
Requires: the backlog skill
Load skills/backlog/skill.md first. It is the canonical reference for every CLI flag, command, ID format (TASK-N / bare integer / ULID), JSON shape, and enum value. This skill assumes you know how to drive the CLI.
In this repo, always pass --profile default (per docs/CLAUDE/MEMORY.md — go test can pollute the profile registry) and --as ai:claude-opus-4-7 (or the current model's exact ID) on every write.
Invocation
/backlog-loop <project> # pull next todo task from <project>, iterate to done, exit
/backlog-loop <project> <ref> # work a specific task (TASK-N, bare integer, or ULID)
/backlog-loop help # print the headless-execution help and exit
If the user omits <project> (and didn't pass help), list available projects and ask which one — do not guess:
./backlog --profile default project list --json
If the user passes help, jump to the Headless execution section below, print it, and exit. Do not pick up a task.
Hard rules
- One task only. The skill never moves to a second task. The user invokes it again if they want more.
- Mandatory Judge gate. The task only moves to
doneafter a[JUDGE RECEIPT]says PASS. The implementing agent never self-marksdone. - Max 5 attempts. Implement → verify → judge counts as one attempt. After 5 failed Judge verdicts, stop and mark the task blocked with a full diagnosis.
- Never expand scope silently. Work discovered mid-execution that's outside the task → new task, not silent expansion of this one.
- Always attribute writes.
--as ai:claude-opus-4-7on every write. - Always
--profile defaultin this repo.
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 · 511 lines · 133 tokens per session scan A da77d4c69358
backlog-loop is a skill published in the GitHub repository mazen160/backlog (15 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 5,687 once invoked, about $0.0007 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
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.
importing-a-codebase
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
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.
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.