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/skill-creatingnpx skills add zalom/plastic --skill skill-creatinggit 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.00128 | $0.00938 |
| Opus 5 | $0.00064 | $0.00469 |
| Sonnet 5 | $0.00026 | $0.00188 |
| Haiku 4.5 | $0.00013 | $0.00094 |
Grade A, and why
plastic-skill-creating 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Skills
Author skills, agents, and hooks as thin routers over deep references. This body carries the rules that must stay correct without opening anything, then routes each authoring task to the reference that holds the depth.
Rules (must be right even if no reference is opened)
- Three load levels, hard budgets: metadata around 100 tokens (always loaded), body under 5000 tokens and under 500 lines (loaded on trigger), references on demand. Keep the body well under budget, not at the ceiling.
- Progressive disclosure first: the body routes, the references hold the depth. Any deep how-to in the body belongs in a reference instead.
- Description states WHEN to use, not the workflow. Write it in third person, front-load concrete trigger keywords, and include at least one indirect trigger (a request that never names the domain). Never summarize the steps.
- Bind every reference link to an observable trigger condition. Never leave a bare pointer to a reference.
- References stay one level deep. Any reference over 100 lines opens with a table of contents.
- Build at least three evals before writing extensive docs.
- Match determinism to fragility: a deterministic script for fragile or repeated mechanical steps, prose for judgment calls.
- Imperative voice, no second person. User-facing docs (README, docs/, AGENTS.md, CLAUDE.md) never use em-dashes or en-dashes, and newly authored skill text avoids them (use commas, periods, parentheses, colons). Existing internal files and the sanctioned template emissions (templates/index.md's INDEX line shape) are not violations.
- The
plastic-prefix is reserved for skills and hooks Plastic itself ships. A skill authored outside Plastic's own tree takes a different name; doctor's ownership checks and the installer's purge both key off the prefix.
Route the authoring task to its reference
| Authoring task | Open |
|---|---|
| Starting any authoring task: load the load-level model and the thin-router pattern first | references/progressive-disclosure.md |
| Authoring an Agent Skill (frontmatter, description, slim body, voice) | references/skills.md |
| Authoring a subagent or Agent role file | references/agents.md |
| Authoring a lifecycle hook | references/hooks.md |
| Deciding script versus prose, or writing a script | references/scripts.md |
| Building evals for a skill | references/evals.md |
What ships with it
9 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.
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 · 76 lines · 128 tokens per session scan A f18116301732
plastic-skill-creating is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 3d ago), licensed MIT. It adds 128 tokens to every session and 938 once invoked, about $0.0006 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.