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 archivegit 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/archive)<a href="https://agentmods.dev/skills/chan4lk/specclaw/archive"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/archive.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.00057 | $0.00475 |
| Opus 5 | $0.00028 | $0.00237 |
| Sonnet 5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
archive 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 8d 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.
What it actually says
specclaw archive
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).
Archive a completed change.
- Validate:
specclaw-validate-change .specclaw <change> archive. If it fails, report and stop. - Verify the change is complete (all tasks done, verification passed, PR merged).
- Record the phase:
specclaw-set-phase .specclaw <change> archived done.specclaw-set-phaseis the only writer of phase state — it recordsstate.jsonand upserts the Archived row instatus.md. Never hand-edit those rows. Run it before the move, so the recorded state travels with the directory. - Move to
.specclaw/changes/archive/<change>/— the name is preserved verbatim, number included, with no date prefix. The leading<NNN>-already orders the folder, and the archive date is recorded instate.jsonby step 3; the old prefix was the archive date, not the change's, so a single bulk archival run stamped 24 of this repo's folders with one identical date — ordering by it was actively misleading. - Update the dashboard:
specclaw-update-status .specclaw. - GitHub sync (if enabled):
specclaw-gh-sync close .specclaw <change>to close the issue. - Azure Boards sync (if
azdo.boards.sync: true):specclaw-azdo-issue close .specclaw <change>to post a closing comment and add aclosed-by-specclawtag. (Does not transition Work Item state — humans drive state in ADO.) - Optionally create a git tag for the release.
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.
- 8d ago First seen · 19 lines · 57 tokens per session scan A 06d56150362c
archive is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 475 once invoked, about $0.0003 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…
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…
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…
changelog
Generate changelogs, release notes, and feature announcements from sprint artifacts. Use when a sprint is complete and needs to be communicated to users. Also use when the user says "changelog", "release notes", "what's new", "announce this", "communicate this feature", "write the update", or after a capture-lessons…
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…