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-goalgit 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-goal)<a href="https://agentmods.dev/skills/derio-net/super-fr/fr-goal"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-goal/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-goal"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-goal.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.00128 | $0.02049 |
| Opus 5 | $0.00064 | $0.01025 |
| Sonnet 5 | $0.00026 | $0.00410 |
| Haiku 4.5 | $0.00013 | $0.00205 |
Grade A, and why
fr-goal 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 2d 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-goal
One operator touchpoint — the batched Q&A — from goal to reviewed PR, driven by a workflow
shape (spec §4.A, 2026-08-14-workflow-shapes-and-workitem-dispatch-design.md): fr run start <shape> --branch <b> (defaults to fr-goal), then loop fr run advance <run-id>.
Shape lookup: repo docs/superpowers/workflows/<shape>.yaml (overrides wholesale) →
$FR_SHIPPED_WORKFLOWS_DIR → the installed fr wheel's own copy → the Claude Code
marketplace clone — so shipped shapes work on a hermes pod or under OpenCode with no plugin
installed. start enters isolation itself and writes the run inside that workspace — the
first action, before anything else ("start with X" changes the first work item, never the
first action); run every later command from the workspace it prints. No devcontainer profile
→ pause for fr-init. kind: cli executes directly — exit code is the verdict, fix and
re-advance on failure. kind: agent never executes itself: it prints a dispatch brief
(skill/agent/needs/emits/tier/for_each) you fulfill per that step below, then fr run resolve <run-id> --step <id> --state done|failed [--emitted name=path ...] (each name must be one
the step emits; a spec/plan path must exist and is stored repo-relative). gate: operator blocks until you resolve it (same command; a gated cli step then runs on the next
advance). Blocked → stop, say what you tried, ask. Another shape, same mechanics; below
narrates the shipped fr-goal shape.
fr refused with "artifacts … must be migrated"? Expected: a pod, CI and an agent's Bash
tool are all non-interactive, where fr never migrates or commits by itself. Run fr migrate artifacts --yes yourself and continue — exempt from that gate, needs no TTY. Work already
in flight when your fr changed under it? fr run adopt <plan-dir|spec> reconstructs a
cursor from what is on disk — completed phases included — so the plan joins the run model
instead of being stranded. Offered, never forced: the migration prints the command (--yes --adopt does all of them) and adopts nothing itself.
Announce at start: "I'm using fr-goal to run this goal autonomously."
Interactive touchpoints (all else autonomous): brainstorm's batched
Q&A (gate: operator — unanswered = stop), with any cross-repo location question folded in;
manual phases from plan; PR merge after deliver — never self-merged — and the post-merge
Test Plan.
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.
- 2d ago Changed · +23 tokens per session a5b7e89c777d
- 9d ago First seen · 121 lines · 105 tokens per session scan A 976975987924
fr-goal is a skill published in the GitHub repository derio-net/super-fr (1 stars, last pushed yesterday), licensed MIT. It adds 128 tokens to every session and 2,049 once invoked, about $0.0006 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
project-setup
One-time interactive setup to configure a project for autonomous development. Use when setting up a new project for TDD-based autonomous development with HCF.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
golang-testing
A guide to testing Go programs, including test-driven development (TDD), table-driven tests, coverage, and debugging. TDD means writing a failing test before implementing the code that makes it pass.
springboot-tdd
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
develop-tdd
Test-driven development with red-green-refactor loop using vertical slices. Use for features (epic tasks) or bugs (specs/bugs/BUG-.md).