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/gantisstorm/essentials-claude-code/tasks-loopgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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.00010 | $0.01203 |
| Opus 5 | $0.00005 | $0.00602 |
| Sonnet 5 | $0.00002 | $0.00241 |
| Haiku 4.5 | $0.00001 | $0.00120 |
Grade A, and why
tasks-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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tasks Loop Command
Execute prd.json tasks iteratively until all tasks are complete.
Note: Loop and swarm are interchangeable - swarm is just faster when tasks can run in parallel. Both enforce exit criteria and sync prd.json.
Uses Claude Code's built-in Task Management System for dependency tracking and visual progress (ctrl+t).
Arguments
prd-path(optional): Path to prd.json (default:./prd.json)--max-iterations N(optional): Maximum iterations before stopping (default: unlimited)
Instructions
Step 1: Read prd.json (Only)
DO NOT read other files, grep, or explore the codebase - just parse the prd.json. Never spawn sub-agents or delegate work — do ALL implementation directly yourself.
cat <prd-path>
Parse the JSON and identify:
- All userStories
- Dependencies (
dependsOnarray) - Priorities (lower number = higher priority)
- Completion status (
passes: true/false)
Step 2: Create Task Graph
Create a task for each userStory and build an ID map as you go:
// Create tasks in order — each returns a task ID
TaskCreate({ "subject": "US-001: Setup database schema", ... }) // → task "1"
TaskCreate({ "subject": "US-002: Implement auth service", ... }) // → task "2"
TaskCreate({ "subject": "US-003: Add login route", ... }) // → task "3"
// ID map: { "US-001": "1", "US-002": "2", "US-003": "3" }
Full TaskCreate per story:
TaskCreate({
"subject": "US-001: Setup database schema",
"description": "<full description from userStory - self-contained>",
"activeForm": "Setting up database schema",
"metadata": { "id": "US-001", "prdPath": "<prd-path>" }
})
Translate dependsOn to addBlockedBy using the ID map:
// prd.json says: US-003 has dependsOn: ["US-001", "US-002"]
// ID map: US-001→"1", US-002→"2", US-003→"3"
TaskUpdate({
"taskId": "3",
"addBlockedBy": ["1", "2"]
})
A task with non-empty blockedBy shows as blocked in ctrl+t. When a blocking task is marked completed, it's automatically removed from the blocked list. A task becomes ready (executable) when its blockedBy list is empty.
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 · 153 lines · 10 tokens per session scan A cb7819a01e26
tasks-loop is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 10 tokens to every session and 1,203 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-30.
Other commands, from other repositories
set-tracker
Set the issue tracker for the current project.
maggy-init
Interactive wizard that configures Maggy for the user's org, issue tracker, and codebases. Writes /.maggy/config.yaml and ensures deps are installed.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.
doncheli-debate
Adversarial multi-role deliberation — PM vs Architect vs QA.