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/project-creatingnpx skills add zalom/plastic --skill project-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.00062 | $0.01540 |
| Opus 5 | $0.00031 | $0.00770 |
| Sonnet 5 | $0.00012 | $0.00308 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
plastic-project-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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating a Project
Precondition
An active intent must exist with enough context to define a project — at minimum: name/slug, path, and key decisions from ## Context > ### Decisions.
Workflow
1. Determine Project Identity
- Slug: derived from intent name (kebab-case, 2-4 words) or user-specified
- Path: from
~/.plastic/config.ymlproject_roots(first entry as default), or user-specified - Confirm path with user before creation
2. Create Project Directory
mkdir -p <project_root>/<slug>
cd <project_root>/<slug>
git init
3. Run plastic-install --local
Invoke plastic-install --local in the project directory. This creates:
.plastic/
├── store/
├── INDEX.md
└── config.yml
4. Populate AGENTS.md
Create AGENTS.md in the project root from the skeleton in
references/project-scaffolding.md ("AGENTS.md skeleton"): read it now and fill in
the project name, governing intent IDs, decisions, and project-specific rules.
5. Create Tactical Mirror
Create the first intent in the project's store at ~/.plastic/projects/{slug}/store/
using the frontmatter, sections, and INDEX.md line in references/project-scaffolding.md
("Tactical mirror intent"), including the Hub multi-intent variant if there is more
than one founding intent.
Directory: ~/.plastic/projects/{slug}/store/1--{slug}/
File: ~/.plastic/projects/{slug}/store/1--{slug}/1--{slug}.md
6. Register in projects.yml
Read ~/.plastic/projects.yml and add the entry shown in
references/project-scaffolding.md ("projects.yml registration block"). For
Hub-spawned projects, parent references the primary founding intent.
7. Provision the Project Store
The provision-project-store verb is the single source of truth for store
creation. Run it after the project is registered in step 6 (the provisioner
requires registration), and before the QMD step:
ruby ~/.plastic/scripts/provision-project-store <slug>
This ensures ~/.plastic/projects/<slug>/store/ exists with .gitkeep, and
writes INDEX.md and project.yml only if missing. It is idempotent, so it is
safe even when the tactical mirror in step 5 already created the store directory.
Do not create the store with an inline mkdir; the provisioner is the only place
a store is made. For a project that is already registered but store-less, use the
plastic-store-provisioning skill instead.
What ships with it
2 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 · 163 lines · 62 tokens per session scan A 1eb8eb86ab9d
plastic-project-creating is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,540 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…
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.