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/conventionsnpx skills add zalom/plastic --skill conventionsgit 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.00061 | $0.00529 |
| Opus 5 | $0.00030 | $0.00264 |
| Sonnet 5 | $0.00012 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
plastic-conventions 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.
What it actually says
Plastic Conventions
The chapters below hold Plastic doctrine that more than one skill needs. Core always-on
conventions stay in ~/.plastic/PLASTIC.md, which is injected at session start. Read a chapter
when the trigger in the second column applies to the work in front of you.
| Chapter | Read it when |
|---|---|
references/knowledge-graph.md |
when creating, linking, curating, or indexing intents and you need the sources-vs-chain doctrine, the tiers of influence, the ## Links projection, or branch-vs-root directory semantics |
references/lifecycle-and-savepoints.md |
when running a lifecycle stage or a savepoint and you need the subagent report-home contract for how an insight reaches the intent |
references/tiers-and-dispatch.md |
when sizing an intent, choosing agent models, routing to the advisor, or writing an auto-mode human report |
references/gates-and-enforcement.md |
when a transition gate blocks you, or before using an audited escape, for the gate mechanics and the logging contract, or when naming, registering, or retiring a hook or skill |
references/locks-and-worktrees.md |
before taking or releasing a delivery lock, and when working with claims, worktrees, solo mode, or the station ledger |
references/completion-and-done.md |
when ending an intent, for what "intent done" means and the End-stage tail |
references/maintenance-and-revisions.md |
before any structural maintenance edit, for WORK vs MAINTENANCE, the revisions.md move-and-record contract, the violation-tag catalog, and the context-economy measurement buckets |
references/roadmaps.md |
when creating, ordering, closing, or consuming a roadmap, for the file format and the status-mirror rule |
Other skills read these chapters directly at
../plastic-conventions/references/<chapter>.md, resolved relative to their own installed
directory. All three harnesses install skills flat into one shared skills root through the same
install_skills_flat call, so that path is harness-independent.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/completion-and-done.md 2.8 KB
- references/gates-and-enforcement.md 3.4 KB
- references/knowledge-graph.md 3.2 KB
- references/lifecycle-and-savepoints.md 682 B
- references/locks-and-worktrees.md 9.9 KB
- references/maintenance-and-revisions.md 16 KB
- references/roadmaps.md 2.9 KB
- references/tiers-and-dispatch.md 9.4 KB
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 · 32 lines · 61 tokens per session scan A 092b4794c9a8
plastic-conventions is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 529 once invoked, about $0.0003 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…
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.
codedrobe-theme
Create, inspect, convert, apply, replace, verify, troubleshoot, update, publish, or restore reversible CodeDrobe themes for supported Chromium/Electron AI desktop apps, including OpenAI Codex, Tencent WorkBuddy, QoderWork (CN/global), and TRAE SOLO (global/CN). Use when a user asks to turn an attached or local…
levelup-clarify
Review, accept, reject, or defer Context Directive Records (CDRs) discovered by levelup-init or proposed by levelup-specify. Interactive one-CDR-at-a-time workflow.