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 skills add derio-net/super-fr --skill fr-dispatchgit 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-dispatch)<a href="https://agentmods.dev/skills/derio-net/super-fr/fr-dispatch"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-dispatch/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/skills/derio-net/super-fr/fr-dispatch"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-dispatch.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.00054 | $0.01428 |
| Opus 5.5 | $0.00022 | $0.00571 |
| Sonnet 5.5 | $0.00011 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
fr-dispatch 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 17d 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-dispatch
Wraps the fr apply CLI. The single command renders the plan, observes
GitHub state, diffs, and emits the mutations needed to bring GitHub in line
with the plan. Works for first-time creation, incremental updates, and
ongoing reconciliation — there's no separate "first dispatch" verb in v2.
v3: tracking vs queue
Plain fr apply is TRACKING-ONLY (attribute labels, no queue
lifecycle). Queueing is explicit: fr apply <dir> --to vk --yes
adds fr:ready + runner:vk, validates the runner against the
fr.runners registry, and enforces the reachability gate (remote
runners pull the repo; tracking-only applies never pay it). The runner
choice lives ON THE ISSUE as labels — never in plan files.
fr undispatch dequeues; per-phase mixing is legal.
Pre-flight (mandatory)
- Audit first, with the read-only verb:
fr status <plan-dir>— safely allowlistable, never mutates. Read the header line (created date + age, tick counts, dispatch state) and the per-phase table. A locally-complete plan shows "would refuse create"; if the plan is genuinely done, runfr archive <plan-dir>instead of dispatching. Spec rows Unreachable for plans that exist locally = stale refs —fr repair --yesnormalizes them (File cells are bare slugs as of the 2026-06-06 spec-path-repair design). - Never-dispatched plan? Search the target repo for evidence the
work already landed (the stoa incident: 0/59 steps ticked, but 15
merged PRs and the deliverable tree existed in the target repo).
List the merged PRs matching the plan/spec slug, and read the file
at each of the plan's deliverable paths, on the target's forge (on
GitHub:
gh pr list --repo <target> --state merged --search "<slug>"andgh api repos/<target>/contents/<path>). Evidence found → STOP and reconcile with the operator; do not dispatch. - The plan and its referenced spec MUST be merged to the default
branch before running
fr apply --yes. The CLI refuses with exit 2 otherwise, listing the unreachable paths. If you've just written the plan, open a PR for spec+plan and merge it before running this workflow. The dispatch + writeback is then a separate (small) PR — see step 5.
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.
- 17d ago Changed · +1 lines 3152b7510000
- 1mo ago First seen · 120 lines · 54 tokens per session scan A a49e412d8b5c
fr-dispatch is a skill published in the GitHub repository derio-net/super-fr (2 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,428 once invoked, about $0.0002 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 skills, from other repositories
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).
stale-proposals
Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.