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 agentmods add skills/joris887/exosuit/undo-worknpx skills add joris887/exosuit --skill undo-workgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/undo-work)<a href="https://agentmods.dev/skills/joris887/exosuit/undo-work"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/undo-work.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 | $0.00018 | $0.01016 |
| Opus 5 | $0.00009 | $0.00508 |
| Sonnet 5 | $0.00004 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
undo-work 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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
undo-work
Safely undo work when an implementation attempt has gone wrong. Provides structured rollback with safeguards against accidental data loss.
Arguments: $ARGUMENTS
1. Assess Current State
git status
git log --oneline -10
git stash list
Determine the situation:
- Uncommitted changes only → Soft or hard reset options
- One or more commits on feature branch → Revert commits or reset branch
- Mid-story-cycle → Full story rollback
Present findings to the user before proceeding.
2. Confirm Scope with User
Show the user:
- Files that will be affected (list modified/added/deleted files)
- Commits that will be reverted (if any)
- Whether there's uncommitted work at risk
Ask the user to confirm one of these rollback levels:
| Level | What it does | When to use |
|---|---|---|
| Soft | Stash uncommitted changes (recoverable via git stash pop) |
"Let me save this aside and try a different approach" |
| Hard | Discard all uncommitted changes | "This attempt is wrong, start fresh from last commit" |
| Story | Reset branch to before the story's commits | "The whole story implementation needs to restart" |
3. Execute Rollback
Soft (stash)
git stash push -m "undo-work: <user-provided reason or auto-description>"
Report: "Changes stashed. Use git stash pop to recover if needed."
Hard (discard uncommitted)
git diff --stat # Show what will be lost — confirm with user
git stash push --include-untracked -m "undo-work: <user-provided reason>"
git stash drop # Discard the stash (changes intentionally discarded)
This captures both tracked changes AND untracked files into a stash, achieving a clean working directory. If the user changes their mind before the drop, git stash pop recovers everything.
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.
- 3d ago First seen · 135 lines · 18 tokens per session scan A 1410dbfad559
undo-work is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 14d ago), licensed MIT. It adds 18 tokens to every session and 1,016 once invoked, about $0.0001 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-31.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
linkedin-post
You take a YouTube video transcript and produce a single LinkedIn post draft.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
source-command-ccguide-daily
Daily update check — official Anthropic docs diff + guide/CC releases digest.