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 commands/blackpaw-studio/leo/work-nextgit clone --depth 1 https://github.com/blackpaw-studio/leoWrote 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/commands/blackpaw-studio/leo/work-next)<a href="https://agentmods.dev/commands/blackpaw-studio/leo/work-next"><img src="https://agentmods.dev/badge/commands/blackpaw-studio/leo/work-next.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.01917 |
| Opus 5 | $0.00014 | $0.00958 |
| Sonnet 5 | $0.00005 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade C, and why
work-next scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf` worktrees. Leave them for post-mortem; they GC when `git worktree prune` runs after the branch is deleted. How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/work-next — one iteration of the Leo kanban dev loop
You are the builder agent. A separate reviewer agent runs on PRs — your job ends when you push a PR.
This command does one iteration against the Leo Kanban board (https://github.com/orgs/blackpaw-studio/projects/3). A second agent runs /loop Nm /work-next to repeat. Do not loop inside this command.
Prerequisites (verify silently, abort with a clear message if missing)
ghCLI authenticated withproject+reposcopesgitconfigured with push access toblackpaw-studio/leo- Working directory is a checkout of
blackpaw-studio/leoon a cleanmain
Run these checks first. If anything fails, print the problem and stop.
gh auth status
git rev-parse --show-toplevel
git status --porcelain
Constants
- Project number:
3 - Project owner:
blackpaw-studio(org) - Repo:
blackpaw-studio/leo - Worktree root:
~/.leo/worktrees/leo
Fetch the board
Use gh project item-list 3 --owner blackpaw-studio --format json --limit 50 to pull all items. Filter client-side for status == "Todo" (single-select field Status). Sort by issue number ascending — lowest number is top of queue.
If no Todo items: print no cards in Todo — nothing to do and exit 0.
Pick one card
Take the first (lowest-numbered) Todo item. Call it $ISSUE. Capture:
issue_numbertitlebody- existing labels
- all comments (via
gh issue view $ISSUE --repo blackpaw-studio/leo --json body,comments,labels) - the project item id (for status updates)
State machine — decide what this iteration does
Evaluate in order. Each branch ends the iteration (no fall-through).
1. Card has label agent-skip
Skip it. Move on to the next Todo card. If none, exit.
2. Card has label needs-info and no new user comments since the last agent [needs-info] comment
Still waiting on the user. Skip. Take next Todo card.
3. Card has label needs-info and the user has replied since your last [needs-info] comment
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.
- 4d ago First seen · 236 lines · 27 tokens per session scan C 7bd39ac0dbbf
work-next is a command published in the GitHub repository blackpaw-studio/leo (5 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 1,917 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
tasks
Command "tasks" from thrashr888/agentkernel, covering durable tasks, use up to four task workers (the default) and bound active tasks explicitly.
execute
Use the task creator to execute a task epic.
task
Use the task creator to plan and execute a task epic.
sprint-start
Abre uma sprint — cria a branch, o doc da sprint e o objetivo com DoD. Use quando disser "vamos começar a sprint" ou ao terminar a anterior.
statuswt
You are checking the status of all active worktree task files in the project.
sprint-close
Fecha a sprint ativa — atualiza changelog e session log, checa a DoD e prepara a tag. Use ao dizer "fecha a sprint" ou "terminei essa etapa".