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/implement-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.00007 | $0.00836 |
| Opus 5 | $0.00003 | $0.00418 |
| Sonnet 5 | $0.00001 | $0.00167 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
implement-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 yesterday.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Loop Command
Execute implementation from conversation context and task description. Loops until exit criteria pass.
Note: Loop and swarm are interchangeable - swarm is just faster when tasks can run in parallel. Both enforce exit criteria and sync state.
Source: Conversation context + argument input + mentioned files.
Uses Claude Code's built-in Task Management System for dependency tracking and visual progress (ctrl+t).
Arguments
<task description>(required): What to implement (e.g., "fix the auth bug we discussed", "add the login feature")
Instructions
Step 1: Create Task Graph Immediately
ONLY use what's already available:
- The user's argument input
- Conversation history (already in context)
DO NOT:
- Read files unless the user explicitly asks you to
- Grep or explore the codebase
- Use Glob to find files
- Spawn sub-agents or delegate work — do ALL implementation directly yourself
Create tasks immediately from context. Include file paths in task descriptions so they can be read during execution.
For each work item, create a task:
TaskCreate({
"subject": "Fix auth token validation",
"description": "Full implementation details from context",
"activeForm": "Fixing auth token validation"
})
Set dependencies with addBlockedBy — identify which tasks depend on others completing first:
// Task 2 needs the type fix from task 1
TaskUpdate({
"taskId": "2",
"addBlockedBy": ["1"]
})
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.
Step 2: Execute Tasks Sequentially
For each task (in dependency order):
- Claim:
TaskUpdate({ taskId: "N", status: "in_progress" }) - Read files as needed: Use Read tool on file paths from task description
- Implement: Make changes based on context
- Verify: Run any task-specific verification
- Complete:
TaskUpdate({ taskId: "N", status: "completed" }) - Next: Find next unblocked task via TaskList
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.
- yesterday First seen · 123 lines · 7 tokens per session scan A 3b82808af242
implement-loop is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 7 tokens to every session and 836 once invoked, about $0.0000 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
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.