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 jmagly/aiwg --skill rollback-workspacegit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/rollback-workspace)<a href="https://agentmods.dev/skills/jmagly/aiwg/rollback-workspace"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/rollback-workspace/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/jmagly/aiwg/rollback-workspace"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/rollback-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 29 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 61 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 178 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00025 | $0.01484 |
| Opus 5 | $0.00013 | $0.00742 |
| Sonnet 5 | $0.00005 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
rollback-workspace 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 7d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rollback Workspace
You restore the .aiwg/ directory from a backup created by migrate-workspace. Lists available backups when no specific backup is named. The restore is safe — it will not overwrite artifacts that were created after the migration.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "undo the migration" → rollback to most recent backup
- "restore my workspace" → rollback to most recent backup
- "what backups do I have?" → list available backups
- "revert aiwg directory" → rollback to most recent backup
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Rollback latest | "roll back the workspace migration" | Run aiwg rollback-workspace |
| List backups | "what workspace backups exist?" | Run aiwg rollback-workspace --list |
| Specific backup | "restore from the backup made on April 1st" | Run aiwg rollback-workspace --from .aiwg/.backup-20260401-1423 |
| Dry run | "preview the rollback" | Run aiwg rollback-workspace --dry-run |
| Force | "rollback workspace, skip confirmation" | Run aiwg rollback-workspace --yes |
Behavior
When triggered:
-
List backups before restoring unless a specific backup is named or the user has already confirmed:
- Run
aiwg rollback-workspace --listto show what is available. - If only one backup exists, propose it directly.
- If multiple backups exist, ask which one to restore.
- Run
-
Extract arguments:
- Is
--listrequested? Show backups and stop. - Is a specific
--from <path>given? Use that backup. - Is
--dry-runrequested? Show what would be restored, no changes. - Has the user confirmed? Use
--yesto skip the interactive prompt.
- Is
-
Run the appropriate command:
# List available backups aiwg rollback-workspace --list # Preview rollback (no changes) aiwg rollback-workspace --dry-run # Rollback to most recent backup (prompts for confirmation) aiwg rollback-workspace # Rollback to specific backup aiwg rollback-workspace --from .aiwg/.backup-20260401-1423 # Rollback, skip prompt aiwg rollback-workspace --yes
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.
- 7d ago First seen · 179 lines · 25 tokens per session scan A 4a407ed0a192
rollback-workspace is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 1,484 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-09-05.
Other skills, from other repositories
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-class-cycle
Run one DOS plan-class lifecycle tick from the workspace [lifecycle] table: evaluate declared transitions, have a judge approve/defer them, write gated plan-meta edits, and log the cycle. Use when gardening plan lifecycle classes automatically.
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
task-copilot
Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context.