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/zalom/plastic/uninstallnpx skills add zalom/plastic --skill uninstallgit clone --depth 1 https://github.com/zalom/plasticWrote 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/zalom/plastic/uninstall)<a href="https://agentmods.dev/skills/zalom/plastic/uninstall"><img src="https://agentmods.dev/badge/skills/zalom/plastic/uninstall.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.00060 | $0.00713 |
| Opus 5 | $0.00030 | $0.00357 |
| Sonnet 5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade C, and why
plastic-uninstall scanned grade C with 2 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -n plastic ~/.claude/settings.json # -> no plastic hook/plugin refs Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls ~/.claude/skills | grep '^plastic-' # -> no output How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uninstall Plastic
The installer tracks every file it writes in a manifest, so uninstall is exact and leaves no orphans. Prefer running it through the CLI; this skill wraps the same underlying uninstaller and adds reporting + verification.
Channel rule
If Plastic is installed, derive <channel> from ~/.plastic/VERSION: a version containing
-alpha means @alpha, -beta means @beta, otherwise @latest. If not installed,
default to @latest. The user can always override with --alpha / --beta / --latest.
Procedure
Step 1: Run the uninstaller
npx -y @zalom/plastic@<channel> uninstall --claude
(Use --codex / --hermes / --all to target other agents. bunx -y @zalom/plastic@<channel> uninstall --claude works too.)
This removes, for the targeted agent:
- all
~/.claude/skills/plastic-*/skills - all
~/.claude/hooks/plastic-*hooks (and restores any saved original statusline) - the
~/.claude/plastic/state dir + manifest - any legacy plugin layout:
plugins/marketplaces/plastic,plugins/cache/plastic, the old nestedskills/plastic/, and theplastic@plastic/extraKnownMarketplaces.plastic/known_marketplaces.jsonregistrations
Step 2: Report removed vs left
Relay the uninstaller's output to the user: what was removed and what was left in place.
- Left:
~/.plastic/(intent store, history, projects) and any non-Plastic settings.json entries.
Step 3: Verify removal
Tell the user to confirm:
ls ~/.claude/skills | grep '^plastic-' # -> no output
ls ~/.claude/hooks | grep '^plastic-' # -> no output
grep -n plastic ~/.claude/settings.json # -> no plastic hook/plugin refs
Step 4: Report
Emit the reporting block, using the Step 3 checks for the verification line:
Plastic uninstall (<channel>)
Command: npx -y @zalom/plastic@<channel> uninstall --claude <flags>
Version: removed
Verification: <Step 3 results, or "clean">
Then:
Plastic is uninstalled from [agent].
Your intent store at ~/.plastic/ is untouched.
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.
- 4d ago First seen · 76 lines · 60 tokens per session scan C f74152ed5fcc
plastic-uninstall is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 713 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
agent-spec-tool-first
CRITICAL: Use for agent-spec CLI tool workflow. Triggers on: agent-spec, contract, lifecycle, guard, verify, explain, stamp, checkpoint, plan, requirements, work-units, knowledge requirements, KLL, docs vs knowledge, spec verification, task contract, spec quality, lint spec, run log, "how to verify", "how to use…
agent-spec-authoring
CRITICAL: Use for writing and editing agent-spec .spec/.spec.md files. Triggers on: write spec, create spec, edit spec, new spec, spec authoring, task contract, .spec file, .spec.md file, BDD scenario, acceptance criteria, completion criteria, test selector, boundary, constraint, intent, decision, out of scope, "how…
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.