Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jmagly/aiwgnpx agentmods add skills/jmagly/aiwg/workspace-resetWrote 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/workspace-reset)<a href="https://agentmods.dev/skills/jmagly/aiwg/workspace-reset"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/workspace-reset/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/workspace-reset"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/workspace-reset.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.00016 | $0.02539 |
| Opus 5 | $0.00008 | $0.01269 |
| Sonnet 5 | $0.00003 | $0.00508 |
| Haiku 4.5 | $0.00002 | $0.00254 |
Grade C, and why
workspace-reset scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .aiwg && cp -r $backup_dir .aiwg How it starts
The opening of the file, as written. The whole thing — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill access pattern (post-kernel-pivot, 2026.5+)
Skill names referenced in this document are AIWG skills, not slash commands. Most are not kernel-listed and cannot be invoked as
/skill-nameby the platform. Reach them via:aiwg discover "<capability>" aiwg show skill <name>Only kernel-listed skills (
aiwg-doctor,aiwg-refresh,aiwg-status,aiwg-help,use,steward) are directly invokable as slash commands. See skill-discovery rule.
Workspace Reset
Completely wipe the .aiwg/ directory to start fresh. Optionally backs up existing content and can reinitialize with fresh intake templates.
Parameters
| Flag | Description |
|---|---|
project-directory |
Project root (default: .) |
--backup |
Create timestamped backup before wiping |
--keep-intake |
Preserve .aiwg/intake/ directory |
--keep-team |
Preserve .aiwg/team/ directory (team profile, assignments) |
--reinitialize |
Run intake wizard after reset |
--force |
Skip confirmation prompts |
--dry-run |
Preview what would be deleted |
Use Cases
- Project Pivot - Requirements changed significantly, need fresh start
- Framework Upgrade - Clean slate for new AIWG version
- Corrupted State - Artifacts became inconsistent
- Learning Project - Experimented, ready to start properly
- Handoff Cleanup - Removing trial work before official start
Execution Steps
Step 1: Analyze Current State
Inventory what will be deleted:
# Count files by category
echo "=== Workspace Contents ==="
for dir in .aiwg/*/; do
count=$(find "$dir" -type f 2>/dev/null | wc -l)
size=$(du -sh "$dir" 2>/dev/null | cut -f1)
echo "$(basename "$dir"): $count files ($size)"
done
Report:
Workspace Reset Analysis
========================
Current .aiwg/ contents:
intake/ 3 files (12 KB)
requirements/ 15 files (45 KB)
architecture/ 12 files (78 KB)
planning/ 8 files (23 KB)
risks/ 4 files (8 KB)
testing/ 7 files (34 KB)
security/ 5 files (15 KB)
team/ 2 files (4 KB)
working/ 9 files (28 KB)
archive/ 14 files (56 KB)
reports/ 6 files (19 KB)
─────────────────────────────────
TOTAL: 85 files (322 KB)
Git Status:
Tracked: 45 files (committed)
Untracked: 40 files (local only)
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 · 360 lines · 16 tokens per session scan C 408dc6b979ac
workspace-reset is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 2,539 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.