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 skills/choiyounggi/dev-loop/loop-implementnpx skills add choiyounggi/dev-loop --skill loop-implementgit clone --depth 1 https://github.com/choiyounggi/dev-loopWhat 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.00094 | $0.04036 |
| Opus 5 | $0.00047 | $0.02018 |
| Sonnet 5 | $0.00019 | $0.00807 |
| Haiku 4.5 | $0.00009 | $0.00404 |
Grade A, and why
loop-implement 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop-implement — the single implementation loop, driven by a wiki-plan
Drive work to "done" through a closed, methodology-grounded loop (sources at the
bottom). This is dev-loop's one and only implementation skill — it both plans
(via wiki-plan, step 2) and executes, so there is no separate executor. The
plan wiki-plan produces is not a loose sketch: it fixes an ordered task list
and, for each task, navigates to the exact wiki pages that ground it (the
decision→page map). This loop consumes that plan directly — executing the
tasks in the plan's order, loading exactly the wiki pages each task names, and
citing them — so every change traces back to a verified wiki page.
It works the same whether it runs standalone (you produce the plan here in step 2) or as an orchestrated worker (the orchestrator hands you a task brief and the plan it already produced, and you adopt and implement it here). Either path, one loop.
When to use
- Use: logic changes, new features, bug fixes, behavior-changing refactors.
- Skip: typos, config values, simple rename/import cleanup, one-line edits.
Two entry modes (both run the SAME loop)
- A plan already exists (a
plans/<feature>/from a priorwiki-planrun, or handed to you by the orchestrator): skip producing one — execute its tasks in the## Task ordersequence, one at a time, each through steps 0 and 3–7 below, loading that task's named wiki pages. - No plan yet (a fresh standalone task): step 2 runs
wiki-planfirst to produce the ordered, wiki-navigated plan, then you execute it the same way.
The plan step is fixed (not pluggable)
Step 2 (Plan) is hardwired to the bundled wiki-plan skill and is
mandatory for every non-trivial task — it is not a pluggable role and cannot
resolve to inline planning. wiki-plan grounds each design decision in the
bundled wiki/ semantic layers before any code is written, so the implementing
pass executes decisions instead of guessing them. See step 2 below.
What ships with it
1 file 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.
- yesterday First seen · 282 lines · 94 tokens per session scan A 5a0f4d10d07a
loop-implement is a skill published in the GitHub repository choiyounggi/dev-loop (4 stars, last pushed 2d ago), licensed MIT. It adds 94 tokens to every session and 4,036 once invoked, about $0.0005 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-31.
Other skills, from other repositories
kb-create
Operator procedure to declare and provision a new Knowledge Base GitOps-style, so it survives pod restarts.
kb-import
Agent-guided procedure to import an existing non-OKF wiki or knowledge base (Obsidian vault, markdown folder, wiki export) into a Cartographer KB, incrementally and without big-bang LLM rewriting.
deploy
Rilascia una nuova versione di Cartographer — merge della release PR di release-please, attesa della pipeline GitHub (binari, brew, ghcr), bump del manifest homelab, verifica rollout Flux e update del client locale via brew. Usare quando l'utente chiede di deployare/rilasciare una nuova versione di server e/o client.
implement-plan
Orchestrates implementation of one or more approved plan issues (label plan) into merged PRs through wave planning, delegation to dev subagents in isolated worktrees, coordinator review, and ordered squash-merge with topic-owned documentation conflict resolution. Use when the user asks to implement, ship, or land open…
academic-paper-drafting
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
research-first-development
Build knowledge bases that build software — research before code, teach before execute.