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 chan4lk/specclaw --skill renumbergit clone --depth 1 https://github.com/chan4lk/specclawWrote 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/chan4lk/specclaw/renumber)<a href="https://agentmods.dev/skills/chan4lk/specclaw/renumber"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/renumber/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/chan4lk/specclaw/renumber"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/renumber.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.00111 | $0.00635 |
| Opus 5 | $0.00056 | $0.00318 |
| Sonnet 5 | $0.00022 | $0.00127 |
| Haiku 4.5 | $0.00011 | $0.00064 |
Grade A, and why
renumber 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 9d 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 — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specclaw renumber
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Assign permanent <NNN>- prefixes to change folders that don't have them, so ls reads chronologically.
- Dry run:
specclaw-renumber-changes .specclaw. The tool is dry-run by default — without--applyit prints the plan and makes no filesystem modification whatsoever. If it prints nothing, every folder is already numbered; say so and stop. - Show the user the full
old → newplan, every line of it, not a summary or a count. The plan is the only thing they have to judge before anything moves, and it covers bothchanges/andchanges/archive/. - Get explicit confirmation. A "yes" to this plan and nothing weaker. Renaming is the one destructive operation in this skill; do not infer approval from a user asking a question about the plan.
- Apply: re-run as
specclaw-renumber-changes .specclaw --apply. Ordering is by creation date ascending, ties broken by folder name, so the applied result matches the plan the user just approved. After each rename the change'sstate.jsonis refreshed throughspecclaw-set-phase— the only writer of phase state. - Update the dashboard:
specclaw-update-status .specclaw. The unnumbered-folders hint disappears once the backfill covers every folder. - Confirm the new names to the user.
Refusals and --force
The tool refuses, before any rename, when a change is mid-build (a live worktree or checked-out branch still points at the old path), when a planned target path already exists, or when any folder is already numbered. Report the message and stop — each refusal names something the user must resolve first.
--force overrides only the already-numbered refusal, renumbering every folder from 001 in date order. Its one intended use is recovering from an interrupted --apply, which leaves a mixed part-numbered state that the ordinary run then declines to touch. Use it there and nowhere else: on a healthy repo it rewrites numbers that are already correct and already referenced from commit messages and branch names.
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.
- 9d ago First seen · 23 lines · 111 tokens per session scan A d4aab9fbbefa
renumber is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 5d ago), licensed MIT. It adds 111 tokens to every session and 635 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-30.
Other skills, from other repositories
managing-github
Use when work reaches a GitHub-hosted issue, pull request or review, release, tag, or live deployment-branch boundary, including indirectly after investigation, completed development, or repository policy requires delivery. Also trigger when work discovers a repository defect that may need duplicate search or an issue…
are-we-done
Deterministic close-out gate for a session or work tree. Sweeps a fixed set of sources — the todo list, this session's own promises, git state, TODO/FIXME markers the diff introduced, test and build state, and any issue or ticket referenced — and checks that every open point has been explicitly decided: done, won't…
ship-it
Get the work done in this conversation all the way out — merged, and deployed to every environment the repo has, production included. Grounds itself first in the branches written during this session, the open and closed PRs behind them, and the environments and CI/CD workflows the repo actually defines, then lands and…
pair
Dual-agent development workflow - Claude Code plans and reviews, Codex implements headlessly, git automated. ONLY runs when the user explicitly types /pair. NEVER activate automatically, no matter how well a task seems to match this workflow.
ship-it-now
Same skill as /ship-it, with the ride-along confirmation gate turned off.
capture-lessons
Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…