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-runnernpx skills add derio-net/super-fr --skill fr-runnergit 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-runner)<a href="https://agentmods.dev/skills/derio-net/super-fr/fr-runner"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-runner.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.1 | $0.00083 | $0.00607 |
| Opus 5 | $0.00042 | $0.00303 |
| Sonnet 5 | $0.00017 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00061 |
Grade A, and why
fr-runner 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 5d 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.
What it actually says
fr-runner
The runner is the autonomous consumer of queued phases. The framework
surface is fr_dispatch (discover_plans + tick against the Runner
protocol); the VibeKanban adapter is fr_vk (VkRunner, MCP client,
card/workspace creation, the cron daemon python -m fr_vk.bridge).
Neither is wired into the fr CLI — the daemon consumes them as a
library on its pod.
Health checks
- Is the daemon ticking? The heartbeat gauge
(
willikins_heartbeat_last_success_timestamp) must be recent. Sync/failure counters:willikins_vk_bridge_sync_total,willikins_vk_bridge_failure_total{reason=…}— reasons:project_id_missing,unknown_repo,mcp_error,gh_error. - Is a phase eligible?
fr status <plan-dir>on the plan: a phase dispatches only when its RENDERED labels say ready-but-not-synced, it has atracking_issue, and the plan + spec are on origin/HEAD (the bridge pod pulls; reachability is why dispatch requires merged plans). - Repo known to the runner? The VK adapter refuses repos its board
doesn't list (
unknown_repofailures) — add the repo in VK first.
Common faults
- Queued forever, no failures: pod checkout stale (pull the repo on the pod), or every slot is in use (workspace budget — the runner defers and retries next tick, no action needed).
project_id_missing: the pod env lostVK_DERIO_OPS_PROJECT_ID.- Dispatched in error:
fr undispatch <plan-dir> --yescloses the Issues and nulls the tracking fields; the runner's reaper archives the orphan workspaces on its next pass. - Card exists, workspace missing: set
VK_BRIDGE_RECOVER_ORPHAN_CARDS=1for one tick (opt-in recovery).
Boundaries
This skill OPERATES runners; queueing work to them is fr-dispatch's
ceremony, and implementing phases is fr-execute's. The daemon never
creates Issues (operator-only via fr apply --yes) and never implements
work itself.
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.
- 5d ago First seen · 54 lines · 83 tokens per session scan A c61c2b132600
fr-runner is a skill published in the GitHub repository derio-net/super-fr (1 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 607 once invoked, about $0.0004 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
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…
simplify
Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior.
incremental-analysis
Detect existing workspace, diff current sources against high water mark metadata, classify specs as unchanged/stale/orphaned/new, re-analyze only what changed. Activates automatically when /analyze finds an existing workspace.