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.
npx agentmods add skills/derio-net/super-fr/fr-executenpx skills add derio-net/super-fr --skill fr-executegit 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/skills/derio-net/super-fr/fr-execute)<a href="https://agentmods.dev/skills/derio-net/super-fr/fr-execute"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-execute.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.01310 |
| Opus 5 | $0.00014 | $0.00655 |
| Sonnet 5 | $0.00005 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
fr-execute 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fr-execute
Implements a single phase from a plan.
Announce at start: "I'm using fr-execute to implement this phase."
Mode selection
| Input | Mode |
|---|---|
| Issue URL/number (dispatch repo) | Dispatched: read assignment from Issue body — it embeds the spec link, plan _prose.md, and phase NN.yaml inline (repo checkout stays the source of truth) |
| (plan_dir, phase number) | Local: direct arguments |
PR format (unified)
When creating the PR for an agentic phase:
- Title:
[{owner}/{repo}] {slug} · Phase {n}/{total} · {phase_title}— matches the Issue title shape so VK / GH / PR surfaces align. - Body: first content block is the tracking block copied verbatim from
the Issue body (the
📦 Repo:/📋 Plan:/ … lines plus the**Goal (from plan):**paragraph). Then proceed with your PR summary.
The fr pickup output below provides the canonical PR title template.
Label lifecycle (no manual transition verbs in v2)
The Issue moves: fr:ready → fr:in-progress → fr:pr-ready → closed. v2 has no
manual transition verbs — every label flip is derived from what the
renderer can observe on the Issue plus its linked PRs:
fr:ready: the phase has atracking_issuebut no assignee, no draft PR, and no open non-draft PR.fr:in-progress: the Issue has an assignee OR a draft linked PR.fr:pr-ready: an open non-draft, non-merged linked PR exists.- closed:
state.completion.atis set on the phase AND a merged PR is observed AND no open linked PR remains (per_phase_completeinrender.py).
The fr apply step at the end of the phase pushes whichever transitions the
renderer projects from current GitHub state. To trigger fr:in-progress,
assign yourself to the Issue (or open a draft PR); to trigger fr:pr-ready,
take the PR out of draft.
Procedure
- Get phase scope:
Output is markdown: phase title, dependency reminder, PR title template, tasks + steps, and a pointer tofr pickup <plan-dir> --phase N_prose.mdfor plan-level context. TheDepends on:line surfaces blockers — if any blocker phase is not yetComplete, stop and report.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 121 lines · 27 tokens per session scan A 8433038d8b83
fr-execute is a skill published in the GitHub repository derio-net/super-fr (1 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 1,310 once invoked, about $0.0001 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-31.
Other skills, from other repositories
using-grove
Use when orchestrating a fleet of independent coding agents with Grove from OUTSIDE — isolated per-task workspaces (tmux plus git worktree, host or container) across model providers and harnesses. Triggers on: spinning up, steering, pausing, resuming or killing workspaces, grove create/fleet/show/message/tickets, the…
working-in-grove
Use when you are the coding agent running INSIDE a Grove workspace — a git worktree Grove created for one task, on the host or in a container. Triggers on: reporting or updating your task phase or progress, GROVEPHASEFILE or .grove/phase.json, grove phase, grovesetworkspacephase, naming this workspace or setting its…
configuring-grove
Use when a user wants to set up or change Grove's configuration, for a host/user or for a project. Covers the global user config, the committed project config, machine-local overrides, agents, init scripts, containers, tmux and peek tuning, the TUI theme, the daemon auth, notifications, and ticket providers (Gitea…
reinstalling-grove
Use when a user wants to reinstall, update, or upgrade Grove after pulling new code, or when they report seeing the OLD UI / stale behavior after an update ("I still see the old dashboard", "the redesign isn't showing", "I reinstalled but nothing changed"). Covers the editable uv-tool install model, the…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.