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 skills add minusblindfold/devloop --skill designgit clone --depth 1 https://github.com/minusblindfold/devloopWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/minusblindfold/devloop/design)<a href="https://agentmods.dev/skills/minusblindfold/devloop/design"><img src="https://agentmods.dev/badge/skills/minusblindfold/devloop/design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/minusblindfold/devloop/design"><img src="https://agentmods.dev/badge/skills/minusblindfold/devloop/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.00889 |
| Opus 5.5 | $0.00016 | $0.00356 |
| Sonnet 5.5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
design 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 2mo 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 — 91 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: Write to .work/designs/. Verify with ls before wrapping up.
Constraint: Do not write code. This skill produces a design, not an implementation.
Mode
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.
If $ARGUMENTS (or auto-selected slug) is set → check designs for match (refine), then plans for match (create). No match → print "Run /dl:plan first." and stop. Ambiguous → list and ask. If $ARGUMENTS is empty → list designs; none: fall through to plan picker; one: offer refine or new; many: numbered list. Plan picker: list plans; none → stop; one → auto-select; many → ask.
Task Progress:
- [ ] Determine mode
- [ ] If refine: show current design, ask what to change, iterate, write once
- [ ] Read plan: extract tasks and dependencies
- [ ] Gather context: CLAUDE.md, project scan
- [ ] Ask 2-3 clarifying questions (only unresolved items)
- [ ] Write Overview and Architecture
- [ ] Write Task Specs
- [ ] Write Mermaid diagrams to .work/designs/diagrams/ (see diagrams.md)
- [ ] Write design to .work/designs/
- [ ] Gate: verify design and .mmd files with ls; update active marker
- [ ] Present design for review — primary checkpoint before implementation
Context gathering
Read the plan — extract name, tasks, and dependencies. List them in your response. Read CLAUDE.md if present. Scan the project directory.
Clarifying questions
Ask 2-3 clarifying questions. Read prior artifact decisions — only ask about genuinely unresolved items. Wait for answers.
Task specs
Write a spec for each plan task: Goal, Interfaces, Implementation notes, Acceptance criteria, Tests, Dependencies. In the Tests field, write concrete verification steps that implement can run immediately after completing the slice — not a deferred test plan. Note applicable rules by title (e.g., **Rules:** JPA Entity Rules) — this tells /dl:implement which rule docs from devloop/rules/ to apply.
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.
- 2mo ago First seen · 91 lines · 39 tokens per session scan A e081417ee831
design is a skill published in the GitHub repository minusblindfold/devloop (1 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 889 once invoked, about $0.0002 per session on Opus 5.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-dev
Use this skill when creating or refining Claude Code skill definitions. Skills are model-invoked capabilities that Claude activates autonomously based on context. Helps design focused skills with discovery-optimized descriptions, proper directory structures, and supporting resources. Automatically invoked when user…
command-dev
Use this skill when creating or refining custom Claude Code slash commands. Slash commands are user-invoked reusable prompts that can accept arguments, reference files, and execute bash operations. Helps design command syntax, argument handling, file references, bash execution, and frontmatter configuration.…
coordinator
Runs the research-team plugin's multi-agent research pipeline end-to-end from the main thread: decomposes a topic into 2-5 subtopics, spawns parallel research-team:research-specialist subagents for each, verifies their output on disk, then spawns a research-team:research-report-writer subagent to synthesize the final…
mcp-tool-dev
Create MCP tools — individual tool functions exposed via Model Context Protocol. Use this skill whenever users mention MCP tools, tool handlers, tool functions, tool definitions, or want to add capabilities to an MCP server. Also use when the conversation involves designing tool schemas, writing tool descriptions, or…
report-formats
Output formats and report templates for the research-team plugin's reports. The research-report-writer agent loads this skill for every report. It also applies when a user asks for a research report, technical survey, decision brief, landscape scan, what's-new digest or source summary in a particular editor's format…
slideware
Create visually rich, style-driven slide decks in two output formats: PowerPoint (.pptx via pptxgenjs + React icons) and HTML (single-file Reveal.js deck). Use any time the user asks for a slide deck, presentation, pitch deck, training module, keynote, .pptx file, HTML/web presentation, Reveal.js deck, browser slides…