implement-loop

An implementation command that works through a task in an iterative loop until its exit conditions pass. It creates a task graph from the conversation and performs the implementation directly.

In plain words
What is it for?
Use it to implement or fix a feature from the current conversation, such as repairing authentication or adding a login feature.
Why use it?
It keeps repeated fixing and checking focused on the stated task without requiring separate planning or codebase exploration first.

Command

Install

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.

agentmods
npx agentmods add commands/gantisstorm/essentials-claude-code/implement-loop
Clone the repo
git clone --depth 1 https://github.com/GantisStorm/essentials-claude-code
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 836 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 3b82808af242, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

essentials/commands/implement-loop.md · 123 lines

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):

  1. Claim: TaskUpdate({ taskId: "N", status: "in_progress" })
  2. Read files as needed: Use Read tool on file paths from task description
  3. Implement: Make changes based on context
  4. Verify: Run any task-specific verification
  5. Complete: TaskUpdate({ taskId: "N", status: "completed" })
  6. Next: Find next unblocked task via TaskList

Read the full file on GitHub · 123 lines

Changes

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.

  1. yesterday First seen · 123 lines · 7 tokens per session scan A 3b82808af242

Subscribe to this mod's changes

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.