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-progressnpx 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.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 | $0.00085 | $0.01366 |
| Opus 5 | $0.00043 | $0.00683 |
| Sonnet 5 | $0.00017 | $0.00273 |
| Haiku 4.5 | $0.00009 | $0.00137 |
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 3d 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: archivable + in-progress plans
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 --all # only now, for plans the sweep marked archivable
.md.v1-archive files (from fr migrate v1-to-v2) are pre-migration
originals kept for git-history — leave them; fr archive only moves
the plan folder, not the .v1-archive sibling (a known gap).
How it works (no separate state store)
vk is a single state machine: the plan files (_meta.yaml + NN.yaml) are
the source of truth, and every projection (Issue body / labels / state, spec
table row) is computed on demand. There's nothing to "sync" — fr apply
diffs the projection against observed gh state and emits the mutations
needed to bring them in line.
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.
- 3d 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 (1 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 1,366 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
using-grove
Use when orchestrating a fleet of independent coding agents with Grove from OUTSIDE — isolated per-task workspaces (tmux plus git worktree, host or container) across model providers and harnesses. Triggers on: spinning up, steering, pausing, resuming or killing workspaces, grove create/fleet/show/message/tickets, the…
working-in-grove
Use when you are the coding agent running INSIDE a Grove workspace — a git worktree Grove created for one task, on the host or in a container. Triggers on: reporting or updating your task phase or progress, GROVEPHASEFILE or .grove/phase.json, grove phase, grovesetworkspacephase, naming this workspace or setting its…
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
requirement-forge-refiner
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…
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.