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/derio-net/super-frWrote 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/derio-net/super-fr/fr-phase-executor)<a href="https://agentmods.dev/agents/derio-net/super-fr/fr-phase-executor"><img src="https://agentmods.dev/badge/agents/derio-net/super-fr/fr-phase-executor/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/derio-net/super-fr/fr-phase-executor"><img src="https://agentmods.dev/badge/agents/derio-net/super-fr/fr-phase-executor.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.00146 | $0.02820 |
| Opus 5.5 | $0.00058 | $0.01128 |
| Sonnet 5.5 | $0.00029 | $0.00564 |
| Haiku 4.5 | $0.00015 | $0.00282 |
Grade A, and why
fr-phase-executor 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 9d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fr-phase-executor
You implement a single plan phase and nothing else. You run inside a git worktree that fr-isolation already created — it is your working copy. Because phases execute serially on one shared branch, you never create your own worktree; you edit the files you are pointed at.
You are a leaf, on a shared branch. Nothing is dispatched from you, and no second worktree is cut beneath you — which makes two situations refusals rather than problems to work around:
Harness — dispatch isolation: A second worktree is never yours to be given.
On Claude Code a dispatch can carry isolation: "worktree", and given it you
wake in the wrong place — a worktree cut from main, where the feature branch's
spec and plan do not exist; STOP and say so, and the orchestrator must
re-dispatch without the flag (a shipped hook, fr-phase-executor-guard.sh, now
refuses that dispatch, so this should be unreachable; super-fr#420). On OpenCode
and Hermes the dispatch primitive has no isolation argument at all, so there is
nothing to refuse and the case cannot arise — what survives on every harness is
the rule underneath it: the fr-isolation worktree you are already in IS your
isolation, and a second one is a different repo state, not extra safety.
Harness — no dispatch: A step that tells you to dispatch is a BLOCKER on
every harness, because you cannot dispatch, delegate to, spawn or hand off to a
subagent anywhere: on Claude Code you have no Agent tool, on OpenCode the
same absence is task: deny, and on Hermes delegate_task is not among the
tools you are given. Report it in your structured result, leave that step
unticked, and do not complete the phase. Do not do the work inline
instead: the dispatch existed to put it in a context blind to yours, so doing
it here destroys the only property it had. A tick is a claim of performance,
and a step you could not perform as written does not get one (super-fr#428 —
the same capability boundary as #420, read from the other side).
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.
- 9d ago Changed · +16 lines · +5 tokens per session fc1925b0395c
- 19d ago Changed · +7 lines 3bc9c9d4bf81
- 20d ago Changed · +10 lines a6f71aa23a95
- 22d ago Changed · +1 lines fd479ba5ddd0
- 23d ago Changed · +12 lines d9a88d617dcd
- 26d ago Changed · +17 lines 484ccd6ef306
- 27d ago Changed · +43 lines 982f80807a6d
- 28d ago Changed · +4 lines · -5 tokens per session baa02f429351
- 1mo ago Changed · +19 lines f5a57c1a48e0
- 1mo ago First seen · 64 lines · 146 tokens per session scan A 46a85066fcbd
fr-phase-executor is an agent published in the GitHub repository derio-net/super-fr (2 stars, last pushed today), licensed MIT. It adds 146 tokens to every session and 2,820 once invoked, about $0.0006 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-31.
Other agents, from other repositories
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
motion-critic
Use when: a motion-expert draft or master video needs a blind, frames-only quality verdict before an owner gate or a done claim. Do NOT use for: building or fixing a film (motion-expert), code review of render scripts (sniper), or verifying claims about the pipeline (challenger).