resolve-levels

resolve-levels is a command for Claude Code from dean0x/devflow. It costs 0 tokens per session (689 once invoked), scanned A, original, MIT.

A command that defines which resolution phases run at the standard and lean levels of a workflow. It also lets each worktree, an independent working copy of a repository, use the settings for its own level.

In plain words
What is it for?
It is for configuring triage, fixes, polishing, and technical-debt work across different workflow levels and worktrees.
Why use it?
It makes issue-resolution workflows predictable by specifying which phases run, skip, or use additional rules.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit It is for configuring triage, fixes, polishing, and technical-debt work across different workflow levels and worktrees.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/dean0x/devflow/resolve-levels
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.

Clone the repo
git clone --depth 1 https://github.com/dean0x/devflow

Made for: Claude Code.

Wrote 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.

agentmods badge for resolve-levels

README.md
[![agentmods](https://agentmods.dev/badge/commands/dean0x/devflow/resolve-levels/github.svg)](https://agentmods.dev/commands/dean0x/devflow/resolve-levels)
Your own site
<a href="https://agentmods.dev/commands/dean0x/devflow/resolve-levels"><img src="https://agentmods.dev/badge/commands/dean0x/devflow/resolve-levels/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.

agentmods 80×15 button for resolve-levels

Your own site · 80×15
<a href="https://agentmods.dev/commands/dean0x/devflow/resolve-levels"><img src="https://agentmods.dev/badge/commands/dean0x/devflow/resolve-levels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 689 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00689
Opus 5.5 $0.00000 $0.00276
Sonnet 5.5 $0.00000 $0.00138
Haiku 4.5 $0.00000 $0.00069

Measured 4d ago against content hash c8562e1dab17, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

resolve-levels 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 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.

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.

src/assets/skills/agent-references/references/commands/resolve-levels.md · 26 lines

How it starts

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

Resolve: phases by gate level

Phases

At standard and lean, a row sets its phase at that level. Each worktree reads the column of its own level, except in a global phase. A phase with no row runs as written, and a table with no rows is well-formed.

Phase standard lean
2 Global Triage pass level pass level
6 Polish skip skip

Grammar

  • Phase: 2 Global Triage, 3 Batch FIX_NOW Issues, 4 Fix, 6 Polish or 9 Manage Debt: the number and the text after ### Phase N: in the command, without a trailing parenthetical. Phase 9 never covers 9b or 9c. Any other phase, or a name that does not match its number's heading by this rule, is malformed.
  • Cell: - runs the phase as written; skip, alone, skips it; apply: <name> applies the ## Rules bullet <name>; pass level puts the line GATE_LEVEL: {GATE_LEVEL} first in every spawn prompt of the phase, right after a leading OPERATION: line. A phase with no spawn takes only -. Join apply: and pass level with ; . Each apply: names exactly one bullet. Any other cell is malformed.
  • Rules bullet: a Rules bullet opens - **<name>:**.
  • Skipped: a skipped phase does not stop the run, and the next phase starts as written. A phase that waits for a skipped phase starts at once. Each name on its **Produces:** line reads SKIPPED, and a report shows SKIPPED.
  • Never skip: 2 Global Triage, 3 Batch FIX_NOW Issues, 4 Fix and 9 Manage Debt never take skip. Triage routes each security finding as it does at full. No row leaves a FIX_NOW security finding unfixed, leaves a FIX_SEPARATE item without a ticket, or drops the CI gate. A row or Rules bullet that breaks this rule is malformed, so the command applies no row in any worktree.
  • Global phase: one spawn serves all worktrees in a global phase, as in 2 Global Triage. A global phase uses the strictest level in the run. full is the strictest and lean the least strict. The phase takes that level's cell, and pass level sends that level. At full the phase runs as written.
  • Scope: a row changes only its own phase's spawns and prompts. It adds no shell command, file write, push or GitHub action. It removes no security check, changes neither the Triage security gate nor the ESCALATED route, and keeps the Verification Gate, the CI gate and the compliance directive.
  • Malformed: no ## Phases heading, no | Phase | standard | lean | header, or a row that breaks this grammar. Then the command applies no row in any worktree.

Read the full file on GitHub · 26 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. 4d ago Changed · +1 lines c8562e1dab17
  2. 5d ago Changed · +1 lines 01657a6c7111
  3. 8d ago First seen · 24 lines · 0 tokens per session scan A 64ad53c07c7a

Subscribe to this mod's changes

resolve-levels is a command published in the GitHub repository dean0x/devflow (20 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 689 tokens. 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-18.