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 uninstall-plugingit 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/uninstall-plugin)<a href="https://agentmods.dev/skills/jmagly/aiwg/uninstall-plugin"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/uninstall-plugin/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/uninstall-plugin"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/uninstall-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.01106 |
| Opus 5.5 | $0.00008 | $0.00442 |
| Sonnet 5.5 | $0.00004 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
uninstall-plugin 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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uninstall Plugin
You remove a previously installed Claude Code marketplace plugin. In AIWG vocabulary, the plugin is the delivery wrapper; the deployed files are its extension, addon, or framework payload. You remove deployed files and unregister the wrapper from the local plugin registry.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "get rid of the voice plugin" → uninstall voice@aiwg
- "I don't need the marketing kit anymore" → uninstall marketing@aiwg
- "clean up the SDLC agents" → uninstall sdlc@aiwg
- "remove everything from that plugin" → uninstall with cleanup
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Uninstall plugin | "uninstall plugin voice@aiwg" | Run aiwg uninstall-plugin voice@aiwg |
| Remove plugin | "remove plugin marketing@aiwg" | Run aiwg uninstall-plugin marketing@aiwg |
| Plugin uninstall | "plugin uninstall sdlc@aiwg" | Run aiwg uninstall-plugin sdlc@aiwg |
| Dry run | "what would removing the voice plugin delete?" | Run aiwg uninstall-plugin voice@aiwg --dry-run |
| Keep artifacts | "remove the plugin but keep my .aiwg/ files" | Run aiwg uninstall-plugin sdlc@aiwg --keep-artifacts |
Behavior
When triggered:
-
Extract intent:
- Which plugin is being removed?
- Is this a dry run (preview) or should changes be applied?
- Should project artifacts in
.aiwg/be preserved? (default: yes, always preserve)
-
Run the appropriate command:
# Uninstall a plugin aiwg uninstall-plugin sdlc@aiwg aiwg uninstall-plugin voice@aiwg aiwg uninstall-plugin marketing@aiwg # Preview what would be removed aiwg uninstall-plugin sdlc@aiwg --dry-run # Keep .aiwg/ project artifacts even if plugin-owned (default behavior) aiwg uninstall-plugin sdlc@aiwg --keep-artifacts -
Report the result — list what was removed (agents, commands, skills, rules) and confirm the marketplace wrapper is deregistered.
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.
- 1mo ago First seen · 126 lines · 20 tokens per session scan A b20eb0e90e09
uninstall-plugin is a skill published in the GitHub repository jmagly/aiwg (227 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,106 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
rally
Orchestrating multi-session parallel execution via Claude Code Agent Teams API and Codex CLI Subagents — launch, manage, coordinate concurrent tasks. Use when parallel work is needed.
void
Verifying YAGNI, cutting scope, and proposing complexity reductions. A 'subtraction' agent questioning the justification for every feature, dependency, doc, and config. Does not write code.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development methodology with multi-agent orchestration. Use when running a structured spec-to-code workflow or decomposing a feature through the SPARC phases.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows. Use when piping output between agents/tools as streaming JSON or building a sequential transform pipeline.
cron-scheduler
Schedules recurring or delayed agent tasks. Use for: schedule this, run daily, cron job, set timer.