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/jmagly/aiwg/removenpx skills add jmagly/aiwg --skill removegit 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/remove)<a href="https://agentmods.dev/skills/jmagly/aiwg/remove"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/remove.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.00012 | $0.00713 |
| Opus 5 | $0.00006 | $0.00357 |
| Sonnet 5 | $0.00002 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
remove 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWG Remove
You remove a deployed framework or addon from the current workspace.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "tear down the marketing framework" → remove media-marketing-kit
- "clean up sdlc" → remove sdlc-complete
- "take out the ralph addon" → remove ralph
- "disable the ring methodology" → remove ring-methodology
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Remove framework | "remove sdlc" | Run aiwg remove sdlc-complete |
| Uninstall addon | "uninstall ralph" | Run aiwg remove ralph |
| Remove by full id | "remove media-marketing-kit" | Run aiwg remove media-marketing-kit |
Behavior
When triggered:
-
Extract intent:
- Which framework or addon is the target? Resolve shorthands the same way
usedoes (e.g., "sdlc" →sdlc-complete, "marketing" →media-marketing-kit). - Confirm the item is currently installed before proceeding (check registry).
- Which framework or addon is the target? Resolve shorthands the same way
-
Run the command:
# Remove a framework aiwg remove sdlc-complete # Remove an addon aiwg remove ralph -
Report the result inline — confirm what was removed and note that source files are not deleted (only deployed artifacts and the registry entry are affected).
Examples
Example 1: Remove a framework
User: "remove the sdlc framework"
Extraction: Framework sdlc-complete
Action:
aiwg remove sdlc-complete
Response: "Removed sdlc-complete. Deployed artifacts deleted from .claude/agents/, .claude/commands/, and .claude/rules/. Entry removed from .aiwg/frameworks/registry.json. Source files were not affected."
Example 2: Remove an addon
User: "uninstall the ralph addon"
Extraction: Addon ralph
Action:
aiwg remove ralph
Response: "Removed ralph addon. Deployed artifacts cleared from .claude/. Entry removed from registry."
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.
- yesterday First seen · 102 lines · 12 tokens per session scan A bcb3258202bb
remove is a skill published in the GitHub repository jmagly/aiwg (208 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 713 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-03.
Other skills, from other repositories
archive
File the finished part of the run state into a dated archive — shipped items, research, opportunities, the rotated journal, and handled snags. The live files stay lean; the facts stay on disk.
import-issues
Stage explicitly selected GitHub issues onto the drafting table as quoted source. Never searches, never writes back to GitHub, never installs gh.
status
Read-only shift status — open vs ticked items, parked decisions, snag-log summary, deadline remaining, and any STOP/stall state. Starts no work.
nw-deliver
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
speckit-workflow
Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.
google-tasks-tool
Google Tasks integration for listing task lists and tasks and creating or updating tasks via OAuth2. Use when: fetching TODO lists, adding tasks, marking items complete, or switching task lists.