auto-devflow

A guide for choosing the amount of process needed to handle a software issue, bug fix, feature, or refactor. It scales the workflow from a lightweight path to a more detailed one based on complexity and risk.

In plain words
What is it for?
Use it to select a development mode, coordinate focused sub-tasks, and decide which review and verification phases are needed. It also governs writable work, destructive actions, commits, and final evidence.
Why use it?
It prevents small tasks from carrying unnecessary process while keeping review and verification responsibilities for larger or riskier work. It also keeps scope, approvals, and git safety under the main agent's control.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/konghayao/peri/auto-devflow
Any agent
npx skills add KonghaYao/peri --skill auto-devflow
Clone the repo
git clone --depth 1 https://github.com/KonghaYao/peri

Made for: Claude Code, Codex.

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,459 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00060 $0.04459
Opus 5 $0.00030 $0.02230
Sonnet 5 $0.00012 $0.00892
Haiku 4.5 $0.00006 $0.00446

Measured 2d ago against content hash 092e1f95df70, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auto-devflow 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.

.claude/skills/auto-devflow/SKILL.md · 409 lines

How it starts

The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Adaptive Devflow

Run the lowest sufficient devflow. The main agent remains the controller, but the amount of ceremony and delegation scales with task complexity:

lite < normal < pro < max < ultra

A lower mode may absorb a phase into the controller; it must not discard that phase's responsibility. For example, lite replaces a review subagent with a controller self-review, not with no review.

Non-Negotiables

These rules apply in every mode:

  • The main agent owns scope, mode selection, approvals, TodoWrite, git safety, and final reporting.
  • Use the smallest safe mode, but never trade away correctness, security, or required verification to save steps.
  • Subagents do focused work only. Do not let a subagent silently broaden scope.
  • Run writable phases sequentially. Never run two coding agents against the same checkout at the same time.
  • Ask before destructive operations, branch changes, commits, or scope expansion. Never commit unless the user explicitly requested it.
  • Inspect the actual diff and collect verification evidence before claiming completion.
  • Treat user-visible behavior, public contracts, persistent data, security boundaries, and irreversible operations as risk signals, regardless of file count.

Select a Mode

Accept an explicit mode in forms such as:

/auto-devflow lite fix the typo
/auto-devflow pro implement issue 123
use max mode for this migration

Selection order:

  1. If the user explicitly names a mode, use it as the requested mode.
  2. Scan scope, uncertainty, coupling, reversibility, and verification burden.
  3. Raise the requested mode to any applicable safety floor.
  4. If no mode was named, choose the lowest mode whose conditions all fit.
  5. Perform only enough initial inspection to validate the choice before coding.

Do not ask the user to choose a mode when the evidence is sufficient. State the decision in one line:

Mode: pro — cross-module behavior needs dedicated exploration and independent review.

Read the full file on GitHub · 409 lines

Changes

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.

  1. 2d ago First seen · 409 lines · 60 tokens per session scan A 092e1f95df70

Subscribe to this mod's changes

auto-devflow is a skill published in the GitHub repository KonghaYao/peri (157 stars, last pushed 3d ago), licensed Apache-2.0. It adds 60 tokens to every session and 4,459 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

qa-testing

Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…

openinterpreter/openinterpreter · 77 tokens

plugin-creator

Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries…

openinterpreter/openinterpreter · 86 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openinterpreter/openinterpreter · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openinterpreter/openinterpreter · 113 tokens

skill-creator

Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.

openinterpreter/openinterpreter · 21 tokens

codex-pr-body

Update the title and body of one or more pull requests.

openinterpreter/openinterpreter · 17 tokens