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/updatenpx skills add zalom/plastic --skill updategit 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.00047 | $0.01290 |
| Opus 5 | $0.00023 | $0.00645 |
| Sonnet 5 | $0.00009 | $0.00258 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
plastic-update 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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Plastic
When to Use
- User says "update plastic", "sync plastic", or "upgrade plastic"
- Statusline shows "Plastic update available"
- After a version-bump notification
What it does
update is a single deterministic command. It reads ~/.plastic/VERSION, derives the
channel from the version string (-alpha/-beta/none -> stable), queries npm dist-tags,
and advances to the next version on the current channel. "Already up to date" is a
clean no-op. You do not compute the target yourself, the script does.
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.
Flags
| Flag | Behaviour |
|---|---|
| (none) | Advance to the next version on the current channel |
--latest |
Switch to / advance the stable channel (toward stability, frictionless) |
--beta |
Switch to / advance the beta channel |
--alpha |
Switch to / advance the alpha channel (bleeding edge, confirmed if moving down in stability) |
Switching toward a more stable channel is frictionless; switching toward bleeding edge is
confirmed. To roll back to a previously-installed version, use plastic-rollback.
Prerequisites
Plastic must be installed (~/.plastic/VERSION present). If not, run plastic-install
first (or npx -y @zalom/plastic@latest install --claude directly).
Procedure
Step 1: Run the update
npx -y @zalom/plastic@<channel> update
# channel switch: append --beta / --latest / --alpha
# to target a specific harness instead of every installed one: --claude / --codex / --hermes / --all
bunx -y @zalom/plastic@<channel> update works as a fallback if npx is unavailable.
With no harness flag, update targets every currently-installed harness (read from
each agent's own <agent-dir>/plastic/VERSION), never Claude alone. Pass an explicit flag
only to target one harness specifically.
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.
- 3d ago First seen · 127 lines · 47 tokens per session scan A e943c77cea24
plastic-update is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 1,290 once invoked, about $0.0002 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.