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 YPares/agent-skills --skill jj-todo-workflowgit clone --depth 1 https://github.com/YPares/agent-skillsWrote 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/ypares/agent-skills/jj-todo-workflow)<a href="https://agentmods.dev/skills/ypares/agent-skills/jj-todo-workflow"><img src="https://agentmods.dev/badge/skills/ypares/agent-skills/jj-todo-workflow/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/ypares/agent-skills/jj-todo-workflow"><img src="https://agentmods.dev/badge/skills/ypares/agent-skills/jj-todo-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.03666 |
| Opus 5 | $0.00035 | $0.01833 |
| Sonnet 5 | $0.00014 | $0.00733 |
| Haiku 4.5 | $0.00007 | $0.00367 |
Grade A, and why
jj-todo-workflow 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 11d 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JJ TODO Workflow
The core idea is to use a DAG of empty revisions as TODO markers, representing tasks to be done, and then come back later to edit these revisions to actually do the tasks. This enables structured development with clear milestones. Revision descriptions (i.e. commit messages) act as specifications for what to implement. JJ makes it easy to create such a structure, and then to fill each revision afterwards.
For more information on JJ basics, see the working-with-jj skill. We reuse scripts from that skill here.
This skill talks about two roles: Planners (who lay out the empty revisions and their specs) and Workers (who implement them). Depending on the situation, you may be acting as just Planner, just Worker, or both. It is better to have a good idea of the whole process, but section titles make it explicit which role is most concerned by each section.
Quick Start (Planners & Workers)
Here's a complete cycle from planning to completion (full paths to helper scripts not written):
# 1. Plan: Create a simple TODO chain
jj-todo-create @ "Add user validation" "Check email format and password strength"
# Created: abc123 (stays on current @)
jj-todo-create abc123 "Add validation tests" "Test valid/invalid emails and passwords"
# Created: def456 (@ still hasn't moved)
# 2. Start working on first TODO
jj edit abc123
jj-flag-update @ wip # Now [task:wip]
# ... implement validation ...
# 3. Verify ALL acceptance criteria met
make test # Or equivalent in your project
# 4. Ask to move to next task
jj-todo-next
### ... review current specs (to ensure compliance) and next possible TODOs ...
# 5. Once we're sure everything is properly done, move to next TODO
jj-todo-next --mark-as done def456 # Marks abc123 as [task:done], starts def456 as [task:wip]
That's it! Empty commits as specs, edit to work on them, jj-todo-next --mark-as done <next-step> when FULLY complete.
Status Flags (Planners & Workers)
We use description prefixes to track status at a glance. The [task:*] namespace makes them greppable and avoids conflicts with other conventions.
What ships with it
6 files 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.
- 11d ago First seen · 419 lines · 70 tokens per session scan A 29e103227912
jj-todo-workflow is a skill published in the GitHub repository YPares/agent-skills (30 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 3,666 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
commit
Skill "commit" from clacky-ai/openclacky, covering smart commit skill, critical requirement: single-line commits only, core philosophy, usage and process steps.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
ac-commit-manager
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.
update-skills-from-changelog
Update ElevenLabs agent skills from a merged weekly changelog in elevenlabs-dx, then open a pull request in elevenlabs/skills. Trigger after a changelog merges to main on elevenlabs-dx, or when asked to update skills from changelog YYYY-MM-DD.