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/cookys/autopilot/dev-flow-cardnpx skills add cookys/autopilot --skill dev-flow-cardgit clone --depth 1 https://github.com/cookys/autopilotWrote 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/cookys/autopilot/dev-flow-card)<a href="https://agentmods.dev/skills/cookys/autopilot/dev-flow-card"><img src="https://agentmods.dev/badge/skills/cookys/autopilot/dev-flow-card.svg" alt="Measured on agentmods" 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 | $0.00133 | $0.06398 |
| Opus 5 | $0.00067 | $0.03199 |
| Sonnet 5 | $0.00027 | $0.01280 |
| Haiku 4.5 | $0.00013 | $0.00640 |
Grade B, and why
dev-flow scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`cat .claude/dev-flow-config.md 2>/dev/null || true` How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Flow Evaluation
Project Config (auto-injected)
!cat .claude/dev-flow-config.md 2>/dev/null || true
Model Routing (for subagent dispatch)
!cat .claude/model-routing-config.md 2>/dev/null || true
If no project config above, use defaults from references/model-routing.md.
Dispatch Chains (for orchestrator routing)
!cat .claude/dispatch-config.md 2>/dev/null || true
If no project config above, autopilot's own fallback skills are primary for methodology; native Task dispatch for parallel; autopilot:reviewer for code review. See project-config-template/dispatch-config.md for the schema.
Phase 1: Session Start
Run before any code changes. Size determines which path executes.
S-Size Fast Path
Overhead target under 5 seconds: (1) restate the task in one sentence; (2) branch check
git branch --show-current; (3) proceed to S Workflow — no further gates. S-size skips:
branch freshness, knowledge/digest review, draft plan overlap, risk escalation.
L-Size Full Gates
All gates must pass before any code changes begin; a blocked gate surfaces to the decision-maker (user in normal mode, CEO in CEO mode).
1. Session start SHA: git rev-parse HEAD > .claude/session-start-sha
2. Branch check: git branch --show-current
3. Branch freshness: BEHIND=$(git log HEAD..main --oneline 2>/dev/null | wc -l)
AHEAD=$(git log main..HEAD --oneline 2>/dev/null | wc -l)
→ freshness table below; no main (new repo) = skip.
4. Knowledge review: check .claude/knowledge/ + unprocessed session digests.
5. Draft plan overlap: ls docs/plans/*.md (or project-configured path); overlap with
the current task (same feature/module/story) → normal mode:
confirm with user (proceed vs adopt draft); CEO mode: DOA.
6. Skill routing: per CLAUDE.md / project config, invoke the code-area skills
before writing code. Active enforcement = the L-1.6 TaskCreate
(see L Workflow) — reading this bullet is NOT enough.
What ships with it
5 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.
- 4d ago First seen · 500 lines · 133 tokens per session scan B cb5b0b48fc23
dev-flow is a skill published in the GitHub repository cookys/autopilot (11 stars, last pushed 4d ago), licensed MIT. It adds 133 tokens to every session and 6,398 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…