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.
git clone --depth 1 https://github.com/dean0x/devflowWrote 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/commands/dean0x/devflow/resolve-levels)<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.
<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>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.00000 | $0.00689 |
| Opus 5.5 | $0.00000 | $0.00276 |
| Sonnet 5.5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
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.
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 Polishor9 Manage Debt: the number and the text after### Phase N:in the command, without a trailing parenthetical. Phase9never covers9bor9c. 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## Rulesbullet<name>;pass levelputs the lineGATE_LEVEL: {GATE_LEVEL}first in every spawn prompt of the phase, right after a leadingOPERATION:line. A phase with no spawn takes only-. Joinapply:andpass levelwith;. Eachapply: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 readsSKIPPED, and a report showsSKIPPED. - Never skip:
2 Global Triage,3 Batch FIX_NOW Issues,4 Fixand9 Manage Debtnever takeskip. Triage routes each security finding as it does atfull. 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.fullis the strictest andleanthe least strict. The phase takes that level's cell, andpass levelsends that level. Atfullthe 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
## Phasesheading, no| Phase | standard | lean |header, or a row that breaks this grammar. Then the command applies no row in any worktree.
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 Changed · +1 lines c8562e1dab17
- 5d ago Changed · +1 lines 01657a6c7111
- 8d ago First seen · 24 lines · 0 tokens per session scan A 64ad53c07c7a
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.
Other commands, from other repositories
review-pr
Review a pull request (GitHub) or merge request (GitLab) and provide detailed feedback.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
update
Check for and apply KARIMO updates from GitHub releases.
code-review
Review the current branch changes for bugs and style issues.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
end
End a work session - a settlement pass that reconciles uncommitted / unpushed work + session context into git, the tracker, and a session snapshot file. --session (aliases --snapshot, --pre-compact, --compact) skips settlement and only writes the shared snapshot, keeping the session going.