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/configurenpx skills add choiyounggi/dev-loop --skill configuregit 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.00124 | $0.01088 |
| Opus 5 | $0.00062 | $0.00544 |
| Sonnet 5 | $0.00025 | $0.00218 |
| Haiku 4.5 | $0.00012 | $0.00109 |
Grade A, and why
configure 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
configure — set up the dev-loop tool profile
dev-loop runs fully generic with no config (every role falls back to the
model's own behavior). Configuring the roles makes the loop use your real tools:
your domain wiki for facts, your actual test command for verification, etc. The
bundled best-practice wiki/ (used by wiki-plan) needs no config — the
knowledge role is for a separate external/domain wiki.
Note: the plan step is fixed to
wiki-planand is NOT configurable. There is noplanrole.
Steps
-
Show the current profile. Run and report what is already set vs. default:
sh ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-tools.sh --summary -
Decide scope.
- Global (all your projects):
~/.claude/dev-loop/tools.json - Per-repo (committed, team-shared; overrides global per role/field):
<repo>/.dev-loop/tools.jsonAsk the user which, if unclear. (Legacy~/.claude/loop-orchestrator/tools.jsonand<repo>/.loop-orchestrator/tools.jsonare still read as a fallback.)
- Global (all your projects):
-
Map each role to a real tool. Read
${CLAUDE_PLUGIN_ROOT}/examples/tools.example.jsonas the shape andreferences/tool-profile.mdfor the schema. For THIS environment, detect and propose concrete mappings, then confirm with the user:Role Map to How to find it knowledgeyour domain/policy wiki or knowledge MCP check available MCP servers (e.g. a wiki_search/search_wikitool)verifyyour project's test / build / QA command read package.jsonscripts / Makefile /pom.xml/ CI config for the real commandexplorecode/symbol search (LSP, rtb-sourcecode, ripgrep)what this repo/language supports tacitpast incidents / danger-zone lore (MCP) check for a lore/incidents MCP designFigma / visual-spec MCP only if UI work; check for a Figma MCP intakeissue tracker (orchestrate work-list) Jira/GitHub issues MCP, if used
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 · 72 lines · 124 tokens per session scan A 47c9deb6f69e
configure is a skill published in the GitHub repository choiyounggi/dev-loop (4 stars, last pushed 3d ago), licensed MIT. It adds 124 tokens to every session and 1,088 once invoked, about $0.0006 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.