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 ribeirogab/specwright --skill archivegit clone --depth 1 https://github.com/ribeirogab/specwrightWrote 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/ribeirogab/specwright/archive)<a href="https://agentmods.dev/skills/ribeirogab/specwright/archive"><img src="https://agentmods.dev/badge/skills/ribeirogab/specwright/archive/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/ribeirogab/specwright/archive"><img src="https://agentmods.dev/badge/skills/ribeirogab/specwright/archive.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.00065 | $0.00770 |
| Opus 5.5 | $0.00026 | $0.00308 |
| Sonnet 5.5 | $0.00013 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
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 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
archive — close out a merged change
The one step that happens after the maintainer merges. Every other command
stops before that point: sw:review ends at lgtm and sw:ship ends with it,
because merging is never the agent's call. This skill picks up on the other side
and retires the change folder from the working set.
It does not merge, does not push, and does not review. It confirms and files.
Announce at start: "Archiving the change."
Inputs
$ARGUMENTS names a change folder or slug → use it. Empty → list the changes in
.specwright/changes/*/ whose ticket says status: shipped and ask which; a
single candidate may be used directly.
A change that is not shipped is not archivable. Say which status it carries and
stop — pending or in-progress means the work is unfinished, and blocked
means it needs a decision, not a filing cabinet.
Confirm the merge from git alone
The change's branch is in its task file's branch: frontmatter. Resolve the
default branch, then ask git whether that branch's tip is already an ancestor of
it:
git fetch --quiet origin
default="$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD | sed 's|^origin/||')"
default="${default:-main}"
git merge-base --is-ancestor "<branch>" "origin/$default"
Exit 0 means every commit on that branch is contained in the default branch: it
merged, whatever the remote host is and whoever pressed the button. A non-zero
exit means it did not — stop, report that the branch is not in
origin/<default> yet, and archive nothing.
This check is deliberately host-agnostic. It works on GitHub, GitLab, Gitea, a bare remote on a colleague's machine, or a squash merge that rewrote the commits, because it asks git about containment rather than asking a forge about a pull request.
When the branch no longer exists locally, resolve it from
origin/<branch>; when neither exists, the branch was deleted after merging —
say so and ask the maintainer to confirm the merge before continuing.
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 First seen · 81 lines · 65 tokens per session scan A 7acb09260068
archive is a skill published in the GitHub repository ribeirogab/specwright (3 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 770 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
pr-describe
Draft a pull request description and a matching changelog entry from a branch's diff, in the target repo's own changelog format, without touching GitHub. Determines the PR's commit range (the current branch against its merge-base with the default branch), surveys what changed, then produces a structured PR body plus a…
gsd-complete-milestone
Archive completed milestone and prepare for next version.
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
cloudron-app-publishing
Distribute Cloudron apps via CloudronVersions.json version catalogs.
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.