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-plangit 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-plan)<a href="https://agentmods.dev/skills/derio-net/super-fr/fr-plan"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-plan.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.00036 | $0.01523 |
| Opus 5 | $0.00018 | $0.00762 |
| Sonnet 5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
fr-plan 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 7d 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-plan
Produce implementation plans through collaborative dialogue. Conversational
parts stay here; mechanical parts delegate to the fr plan CLI.
Announce at start: "I'm using fr-plan to create the implementation plan."
Format (v2 plan-as-folder)
A plan is a directory under docs/superpowers/plans/<slug>/ containing:
_meta.yaml— schema_version, plan slug, spec ref, target_repo, vk_version, created date, optional rework metadata (parent_plan,prior_rework,origin_items).specref notation: a same-repo spec is a plain repo-relative path (docs/superpowers/specs/<file>.md). A spec that lives in another repo MUST use the cross-repo form<owner>/<repo>:<path-in-that-repo>(e.g.derio-net/frank:docs/superpowers/specs/<file>.md). Without theowner/repo:prefix,fr apply's reachability gate treats it as a missing same-repo file and refuses to dispatch.fr plan self-reviewwarns when a same-repo-form spec doesn't resolve locally (#248).
_prose.md— the human-readable narrative. Tooling never parses this; it's for humans (and the implementing agent).NN.yaml(one file per phase, two-digit zero-padded:01.yaml,02.yaml, …,99.yaml) — phase header, tasks, steps, and per-step state. Per-phase files prevent merge conflicts when parallel branches tick different phases. Phases are numbered from 1:01.yamlis the first phase;00.yaml(phase 0) fails parse —fr plan createrejects it pre-flight.
Every step id follows P<n>.T<n>.S<n> (phase number, task number, step
number). The renderer / observer / diff / apply chain depends on this shape.
Procedure
- Read context (recent commits, existing plans, spec file).
- Confirm scope. Decompose if too large.
- Propose 2-3 approaches with tradeoffs. Recommend one.
- Present plan structure section by section, get approval.
- Scaffold the plan folder:
fr plan create --slug <YYYY-MM-DD-slug> --target-repo <owner/repo> \ --spec docs/superpowers/specs/<spec-file>.md \ --phases-file <phases.yaml> \ --prose-file <prose.md>fr plan createALSO appends a row to the spec's## Implementation Planstable — there is no separate spec-index step. - Iterate on the prose / per-phase yaml via the Edit tool.
- Run self-review:
fr plan self-review <plan-dir>. - Hand off for execution:
fr apply <plan-dir>— render → observe → diff → preview (default dry-run). Add--yesto actually create / update GitHub Issues.- The implementing agent uses
fr pickup <plan-dir> --phase Nto receive the phase scope as markdown.
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.
- 7d ago First seen · 121 lines · 36 tokens per session scan A 00601e3e2019
fr-plan is a skill published in the GitHub repository derio-net/super-fr (1 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,523 once invoked, about $0.0002 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
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
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.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.