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 runxhq/runx --skill revertgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/revert)<a href="https://agentmods.dev/skills/runxhq/runx/revert"><img src="https://agentmods.dev/badge/skills/runxhq/runx/revert/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/runxhq/runx/revert"><img src="https://agentmods.dev/badge/skills/runxhq/runx/revert.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.00042 | $0.00199 |
| Opus 5.5 | $0.00017 | $0.00080 |
| Sonnet 5.5 | $0.00008 | $0.00040 |
| Haiku 4.5 | $0.00004 | $0.00020 |
Grade A, and why
revert 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 11d 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
Revert
Undo the edits a run made: its fs.write, fs.edit and fs.apply_bundle
calls, named by their call_id. Every file they changed goes back to what it
held before the first of them, in one journaled bundle, so either every file
is restored or none is.
An undo is bound to what the edits left. A file that changed after them is refused, naming it, and nothing is restored: read what changed and decide what to keep before undoing again. A file the edits created is deleted; a file they deleted comes back.
This is an ordinary run with its own receipt, so an undo is as governed as the edit it undoes.
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.
- 11d ago First seen · 20 lines · 42 tokens per session scan A 80eaf0bc70a8
revert is a skill published in the GitHub repository runxhq/runx (105 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 199 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-10-19.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.