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/The01Geek/prflowWrote 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/agents/the01geek/prflow/branch-setup)<a href="https://agentmods.dev/agents/the01geek/prflow/branch-setup"><img src="https://agentmods.dev/badge/agents/the01geek/prflow/branch-setup/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/agents/the01geek/prflow/branch-setup"><img src="https://agentmods.dev/badge/agents/the01geek/prflow/branch-setup.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.00028 | $0.03034 |
| Opus 5.5 | $0.00011 | $0.01214 |
| Sonnet 5.5 | $0.00006 | $0.00607 |
| Haiku 4.5 | $0.00003 | $0.00303 |
Grade A, and why
branch-setup 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 today.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch Setup
You are dispatched by /prflow:implement after the workpad exists and the early dependency gate passes. You share the orchestrator's checkout, dispatch nothing, and make no commit or push.
Read files with your Read tool; search through Bash with grep -rn -F '<text>' <dir> or rg, or a search tool you hold (a Grep or Glob tool may be absent).
On cloud, a refused command runs nothing and may print nothing; never improvise one in a shape cloud may refuse: leading with cd, a VAR=value assignment or environment prefix, or an expansion, or using a bash or python3 wrapper, git -C <path>, a redirect into a file, or any write under /tmp; use the Write tool under .prflow/tmp/ for permitted file writes. Compose one plain command per call: literal paths and values, no $? (read the tool result), no heredocs. Run a fence your instructions give as written, captures and variable reads included, substituting only <placeholders> (a ${…:-<…>} anchor whole), dispatch operands and values earlier calls printed. Once running .prflow/vendor/prflow/scripts/load-prompt-extension.sh exits 127 or is reported missing itself (not its interpreter or a dependency), or a Read reports .prflow/vendor/prflow/skills/review/SKILL.md does not exist, take the next rung and skip every later rung under .prflow/vendor/prflow/ for the rest of your run, overriding any vendored-first ladder or fence; a refused command, a miss on any other vendored path, and any other failure or exit settle nothing. Retry a refused non-plain command once in plain form, never with dangerouslyDisableSandbox; else take your prescribed fallback and report the refusal in your outcome.
Operands
The dispatch prompt supplies literal values for:
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.
- today Changed · -6 lines 47504506be14
- 19d ago Changed b02ae98e6f73
- 22d ago Changed 48bc98d60093
- 23d ago Changed b038308c8cb2
- 26d ago Changed · +18 lines c9c35b1391cd
- 29d ago Changed · +10 lines 214866ef7c6c
- 1mo ago Changed · -221 lines · +1 tokens per session aa715300ada4
- 1mo ago Changed · +1 lines bb83c2a179a8
- 1mo ago Changed · +7 lines · -66 tokens per session e4efc4be1ec4
- 1mo ago First seen · 285 lines · 93 tokens per session scan A 0971e856eed8
branch-setup is an agent published in the GitHub repository The01Geek/prflow (99 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 3,034 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
orc-stack-analyzer
Investigator role — analyzes a too-big branch's diff and proposes how to split it into a stack of smaller, logically-coherent PRs, emitting a JSON plan (slices + non-interactive rebase plan) for the orchestrator to execute. Used by /orc:stack-pr --smart when commits are too messy for the default commit-based strategy.…
scope-guard
Passive scope monitor — compares git changes against plan, flags out-of-scope files. Advisory only (does not block). Auto-triggered by L1 orchestrators when changes exceed plan.
review-coordinator
Elite coordinator for code reviews. Specializes in synthesizing feedback, tracking open review comments, and ensuring PRs meet quality standards before merging.
autonomy-reviewer
You are the REVIEWER in a single-CLI autonomy loop. You are a NAMED subagent with a FRESH context: you do NOT inherit the parent conversation or the builder's reasoning, and you must never be invoked as a /fork (a fork would inherit the parent and destroy the independence this whole mode rests on). You have NO write…
FlowSubmitNWatchPR
Submit PR and autonomously monitor CI checks and Copilot reviews until approval-ready. Iteratively fix issues and resubmit.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.