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-progressgit 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-progress)<a href="https://agentmods.dev/skills/derio-net/super-fr/fr-progress"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-progress/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-progress"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-progress.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.00085 | $0.01436 |
| Opus 5.5 | $0.00034 | $0.00574 |
| Sonnet 5.5 | $0.00017 | $0.00287 |
| Haiku 4.5 | $0.00009 | $0.00144 |
Grade A, and why
fr-progress 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.
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-progress
In v2 there is no dedicated progress subcommand surface — queries decompose into one of three primitives:
| Operator says | Command |
|---|---|
| "audit drift on this plan" | fr apply <plan-dir> (default dry-run lists what gh would change) |
| "status of this spec" | fr spec status <spec-path> |
| "status of every spec" | fr spec status --all |
| "mark step done" | fr plan edit <plan-dir> --tick P<n>.T<n>.S<n> |
| "mark phase done" | fr plan edit <plan-dir> --complete-phase N [--note ...] |
Announce at start: "I'm using fr-progress for [capability]."
Repo-state preflight (run before touching docs/superpowers/ by hand)
First time in a repo with docs/superpowers/ or fr config: never
manually create, move, or archive files under it (#378). Run in order —
fr status/fr repair/fr migrate v1-to-v2 preview by default, no --yes:
fr --help # confirm fr is installed / repo is fr-managed
fr status # repo-wide sweep: four buckets, judged against origin/<default>
fr acceptance check # matrix gate; exit 2 on failing rows
fr repair # preview stale-ref rewrites
ls docs/superpowers/plans/*.md 2>/dev/null || true # hits = legacy v1 plans (v2 is folders)
fr migrate v1-to-v2 # if the ls above found hits
fr spec status --all # per-spec rollup before deciding what's "done"
fr archive docs/superpowers/plans/<name> # only now, one per plan the sweep printed it for
The sweep fetches, then calls a plan merged only when every agentic phase is
complete on origin/<default>; local ticks never count. Buckets: merged but
not archived (each with its own fr archive <plan-dir> line: run those, one
per plan, never --all), merged, manual phases still open (tick them
first), complete locally, not yet on origin/ (waiting for merge,
no command), in progress. merge state unknown = no remote-tracking
default ref (try git fetch / git remote set-head origin -a).
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.
- 5d ago Changed 76a46669ae3c
- 24d ago Changed 5d9060f69b0a
- 1mo ago First seen · 121 lines · 85 tokens per session scan A 80af26728819
fr-progress is a skill published in the GitHub repository derio-net/super-fr (2 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 1,436 once invoked, about $0.0003 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
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
handoff
Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…