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/minusblindfold/devloop/implementnpx skills add minusblindfold/devloop --skill implementgit clone --depth 1 https://github.com/minusblindfold/devloopWhat 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.00038 | $0.01719 |
| Opus 5 | $0.00019 | $0.00860 |
| Sonnet 5 | $0.00008 | $0.00344 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute each section in order. Copy the checklist and check off items as you complete them. Do not proceed past a Gate until verified.
Artifact: The worker writes an implementation note to .work/implementations/ — even if the task is incomplete.
Constraint: You are the foreman — you do not implement tasks yourself. A fresh-context worker subagent implements the selected task; you build its payload, verify its return, and own the plan checkboxes.
Find the feature
Check .work/active/ for marker files. If exactly one exists and no $ARGUMENTS provided, auto-select that feature's slug. If multiple markers exist, list them, offer to archive any with date older than 30 days to .work/archive/, then ask. Arguments always override.
Parse $ARGUMENTS as <slug>, <slug> <task-N>, or <slug> all. If the marker has stage: mini-spec, read the brainstorm artifact's ## Mini-Spec section as the spec — a single task (N = 1), no plan or design required; skip task picking. Otherwise find the plan in .work/plans/ and matching design in .work/designs/. Missing design → print "No design found. Run /dl:design first." and stop. No argument → list plan/design pairs; none: stop; one: confirm; many: ask to pick.
Task Progress:
- [ ] Find plan and design by slug
- [ ] Read plan and design; read completion state from the plan's checkboxes
- [ ] Pick task from args or ask — `all`: require clean tree, then loop per All mode
- [ ] Build the worker payload (task entry, design spec, rules, prior notes)
- [ ] Spawn the worker; receive its structured return
- [ ] Verify: note exists, STATUS complete, tests pass
- [ ] Check off the task in the plan (all mode: commit, then next task or halt)
- [ ] Gate: verify note with ls; update active marker
- [ ] Wrap up: summarize worker return(s), note deviations, suggest commit (all mode: end with forked review's findings)
Load
Read plan and design in full. The plan's - [ ] checkboxes are the authoritative completion state — task numbers are positional. Print the task list with status.
What ships with it
2 files 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 · 89 lines · 38 tokens per session scan A 273aca3ebca8
implement is a skill published in the GitHub repository minusblindfold/devloop (1 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,719 once invoked, about $0.0002 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
skill-creator-advanced
當使用者要建立、改版、測試、評估或發布 skill 時使用。涵蓋 description 優化、evals、benchmark、邊界管理與打包流程。.
writing-for-agents
Writing documents for agents. Use when creating or editing a skill, an AGENTS.md or CLAUDE.md, a subagent definition, a prompt file, or any doc an agent reaches through a pointer.
seed-repo
Seed the current working directory/repo with the coding harness using a python script. Also offers explicit approval-gated installation of harness subagent TOMLs into /.codex/agents.
writing-skills
Guides creation and editing of SKILL.md files following Anthropic best practices and this repo's conventions. Use when creating a new skill, editing an existing skill, porting a skill from another source, or reviewing skill quality. Triggers on "create skill", "new skill", "write skill", "edit skill", "improve skill"…
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…