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/store-curatingnpx skills add zalom/plastic --skill store-curatinggit clone --depth 1 https://github.com/zalom/plasticWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zalom/plastic/store-curating)<a href="https://agentmods.dev/skills/zalom/plastic/store-curating"><img src="https://agentmods.dev/badge/skills/zalom/plastic/store-curating.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00153 | $0.00836 |
| Opus 5 | $0.00077 | $0.00418 |
| Sonnet 5 | $0.00031 | $0.00167 |
| Haiku 4.5 | $0.00015 | $0.00084 |
Grade A, and why
plastic-store-curating 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Curator
Dispatches to the plastic-intent-curator agent for intent store maintenance.
When to Use
- Completing or reviewing intents
- Reorganizing INDEX.md
- Cluster maintenance, orphan detection, link discovery
- Batch status updates
Workflow
Invoke the plastic-intent-curator agent via the Agent tool with subagent_type: "plastic-intent-curator". Pass the user's request as the prompt, including:
- What to do - complete intent, reorganize, triage stale, etc.
- Which store - global (
~/.plastic/) or project (.plastic/store/) - Which intents - by ID or "all active"
The agent handles:
- Intent lifecycle management (status transitions, Outcome sections)
- INDEX.md maintenance (Active/Future/Clusters/Completed/Abandoned sections)
- Link discovery between related intents
- Cluster management (create, merge, rename)
- Orphan detection
Read ../plastic-conventions/references/knowledge-graph.md for the linking doctrine: tiers of
influence, sources versus chain, and the ## Links projection, before judging a link discovery or
orphan finding. This path resolves relative to this skill's own installed directory.
When an intent reaches a terminal state, moved to Completed OR Abandoned, do these things:
- Author a real
outcome.mdin the intent directory from~/.plastic/templates/outcome.md, with the frontmatterdisposition: deliveredfor a completed intent ordisposition: abandonedfor an abandoned one.outcome.mdis MANDATORY at every terminal, delivered and abandoned alike: on abandon it records the abandonment reason and replaces the scaffolded placeholder sentinel (never leaveoutcome.mda placeholder at a terminal). - Call
plastic-intent-endingfor the terminal-transition close (INDEX move, savepointDonebookend, store commit, disarm, and the QMD reindex last):ruby ~/.plastic/scripts/end-intent --store <store> --id <id> --disposition delivered|abandoned, then follow that skill's own disarm and reindex steps. Never restate those one-liners here.
What ships with it
1 file 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.
- 5d ago First seen · 65 lines · 153 tokens per session scan A 744de549d5d8
plastic-store-curating is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 836 once invoked, about $0.0008 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.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
gitnexus
将 GitNexus 作为受控可选代码智能能力接入，用于 brownfield MCP 查询、影响面分析、 detectchanges、多仓分析和更深代码图谱证据。输出必须回落到 /team- 主链和 artifacts。.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.