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 dsnger/dev-workflow-kit --skill candidategit clone --depth 1 https://github.com/dsnger/dev-workflow-kitWrote 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/dsnger/dev-workflow-kit/candidate)<a href="https://agentmods.dev/skills/dsnger/dev-workflow-kit/candidate"><img src="https://agentmods.dev/badge/skills/dsnger/dev-workflow-kit/candidate/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/dsnger/dev-workflow-kit/candidate"><img src="https://agentmods.dev/badge/skills/dsnger/dev-workflow-kit/candidate.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.00073 | $0.02886 |
| Opus 5.5 | $0.00029 | $0.01154 |
| Sonnet 5.5 | $0.00015 | $0.00577 |
| Haiku 4.5 | $0.00007 | $0.00289 |
Grade A, and why
intake 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 5d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
intake
Overview
The front door of the spec-driven workflow. A raw idea or voice transcript goes
in; a reviewable story artifact comes out at
docs/superpowers/stories/YYYY-MM-DD-<topic>-story.md and feeds
superpowers:brainstorming as its input document. This standardizes an entrance
that otherwise varies by whoever writes the prompt.
intake captures WHAT and WHY, never HOW — designing the solution is
brainstorming's job. That boundary governs every story section except
Section 4 (Affected AGENTS.md invariants), which quotes existing project
invariants verbatim as constraints the future solution must respect. Naming a
guardrail the solution has to honor is not designing it — so "auth via the
project's requireAuth barrier" belongs in Section 4, while "add a requireAuth
call to the new handler" is a HOW leak anywhere else.
Target model: Claude via Claude Code. This skill is a prompt artifact and follows
the checklist in docs/prompt-standards.md.
Requires AGENTS.md (the project's invariants file) — the capture route's
invariant-tagging step greps it, and story Section 4 quotes what it finds. If the
repo has none, say so and offer /dev-workflow:workflow-init, which walks you
through writing one.
Choose the route first
intake has two routes that share no steps, so choose one before doing anything else:
| The request | Route | Read in full before its first step |
|---|---|---|
| A raw idea or voice transcript arrives and needs to enter the workflow, before any brainstorming; or a backlog line needs to become a reviewable story before design starts | Capture a new story (the Flow) | capture-new-story.md |
| An approved story or spec must change after a human decided to change it — narrowed, redirected, or corrected for a gap found later | Amend an approved story or spec | amend-approved-artifact.md |
An item that already has an approved story takes the amendment route, however the request
is worded: an approved artifact changes only through the amendment route, never through a
new story. Designing a solution is neither route — that is superpowers:brainstorming.
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.
- 5d ago First seen · 200 lines · 73 tokens per session scan A 7748abf6e146
intake is a skill published in the GitHub repository dsnger/dev-workflow-kit (6 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 2,886 once invoked, about $0.0003 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-10-12.
Other skills, from other repositories
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ring:planning-small-features
Planning the lightweight 4-gate Small Track pre-dev workflow (research, PRD, TRD, plan) with human approval and state tracking at each gate. Use for features under 2 days that reuse existing patterns and add no new dependencies, data models, or services. Skip for larger or complex features — use…