Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/retier/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/retier)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/retier"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/retier/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/rakovi4/continue-framework/retier"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/retier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.02691 |
| Opus 5.5 | $0.00021 | $0.01076 |
| Sonnet 5.5 | $0.00010 | $0.00538 |
| Haiku 4.5 | $0.00005 | $0.00269 |
Grade A, and why
retier 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 1mo 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/retier — One-Shot Tiering Migration
A scenario's tier lives in its Tier: marker inside the story's tests/*.md
(.claude/templates/spec/tier-ladder.md). /retier writes those markers for stories
drafted before tiering existed whose implementation has not started — why that
needs a migration at all, and why a story already under way is left alone, is in
.claude/guidelines/workflow-detail.md, "Bootstrapping".
Run it once, after the merge. /framework-sync's Next Steps routes here when
the merge brings tiering in; the frontmatter description above repeats the run-once
instruction for a hand-merge that never invoked that skill. Afterwards /test-spec
Phase 5 tiers every new story and nothing calls this skill again.
Run it inline in the main agent. It fans out one tiering-agent per story, and
those must not nest inside a wrapper agent. It is never a progress.md checkbox, so
/continue has no dispatch row for it. Stories only — a task has no scenario
set and is never tiered.
Scope by story state
Classify every folder under ProductSpecification/stories/ first, then act.
Never descend into ProductSpecification/stories/done/, and never classify done/
itself as a story folder. This is the one deliberate exception to resolving both
locations (.claude/rules/workflow.md, "Resolving a story folder"): everything in the
archive is complete, which is already the Skip row below — reaching it by walking the
archive would only re-derive that answer, while treating done/ as a story would put a
non-story on the classification path at all.
Test the rows in order; the first match wins — a Done story's tests/ exist and
its checkboxes are [x], so it matches the last two rows too, and only row order
keeps it out of them.
| State | Detected by | Action |
|---|---|---|
| Not specced | no tests/ directory |
Nothing. /test-spec tiers it when it runs. |
| Done | row in the Done table of ProductSpecification/stories.md |
Skip, and say so in the report. |
| Already tier-major | progress.md has a ## Tier N — section |
Nothing — specced after the merge, or migrated by an earlier run. |
| Convertible | tests/ exist, no checkbox below the ## Spec section is [x] |
Tier the set, then re-bootstrap progress.md tier-major. |
| In flight | tests/ exist, at least one checkbox below ## Spec is [x] |
Nothing. Left untiered permanently. |
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.
- 1mo ago Changed · -8 lines c269312c2cb1
- 2mo ago First seen · 187 lines · 52 tokens per session scan A b60b66126ec5
retier is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 52 tokens to every session and 2,691 once invoked, about $0.0002 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.