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/installnpx skills add zalom/plastic --skill installgit clone --depth 1 https://github.com/zalom/plasticWhat 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.00093 | $0.02191 |
| Opus 5 | $0.00046 | $0.01095 |
| Sonnet 5 | $0.00019 | $0.00438 |
| Haiku 4.5 | $0.00009 | $0.00219 |
Grade A, and why
plastic-install 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 2d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Plastic
Recommended path: for a first install, run
npx -y @zalom/plastic@latest install --claudein your shell (orbunx -y @zalom/plastic@latest install --claudeif you use Bun). This skill exists to re-install or repair an existing setup from inside the agent, and to drive interactive global configuration. Whenever this skill performs an install or re-install, it runs/plastic-doctorafterward and reports the result.
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
(first install), default to @latest. The user can always override with
--alpha / --beta / --latest.
Re-install / repair
If Plastic is already installed but something is broken (skills missing, hooks not firing, leftover legacy plugin), re-run the installer, it is idempotent, prunes files that no longer ship, and removes any legacy plugin/marketplace layout:
npx -y @zalom/plastic@<channel> install --reinstall --claude
Then run /plastic-doctor and report what it found.
Channel Flags
| Flag | Behavior |
|---|---|
--latest |
Install from the stable channel (default on a first install) |
--beta |
Install from the beta channel |
--alpha |
Install from the alpha channel |
When invoked from within Claude Code (re-install or channel switch), the skill runs the appropriate npx command:
# Stable (default on a first install)
npx -y @zalom/plastic@latest install --claude
# Beta
npx -y @zalom/plastic@beta install --claude
# Alpha
npx -y @zalom/plastic@alpha install --claude
The installed version and channel are recorded in ~/.plastic/VERSION.
Modes
Global Install (default, recommended)
Run /plastic-install with no arguments.
Procedure
Step 1: Run the installer
Check if ~/.plastic/VERSION exists.
- If yes: announce "Plastic is already installed at ~/.plastic/. Run
/plastic-updateto sync core files, or use the re-install command above to repair in place." - If no: first ask the advisor question below (Claude Code only), then run the fresh
install command (default
@latest, or the channel the user named) with whichever flags that answer produced:
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.
- 2d ago First seen · 216 lines · 93 tokens per session scan A 3eef4e10cdd6
plastic-install is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 2,191 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
ss-component
Generate a new UI component following the StyleSeed design conventions.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.