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/intent-speccingnpx skills add zalom/plastic --skill intent-speccinggit 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/intent-speccing)<a href="https://agentmods.dev/skills/zalom/plastic/intent-speccing"><img src="https://agentmods.dev/badge/skills/zalom/plastic/intent-speccing.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 | $0.00171 | $0.01115 |
| Opus 5 | $0.00086 | $0.00558 |
| Sonnet 5 | $0.00034 | $0.00223 |
| Haiku 4.5 | $0.00017 | $0.00112 |
Grade A, and why
plastic-intent-speccing 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Speccing
Consolidate the enriched Why into spec.md through eight fixed steps, one action per step. The
next action is never a judgment call: when a section cannot be filled from what is on record,
step 5 is to stop and ask, never invent.
Precondition
Run only when the active intent is at Why (its ## Intent and enriched ## Context plus
### Decisions exist, spec.md does not yet exist or is being redone) and the user has asked to
consolidate that Why into the spec. If no intent is active, or the active intent is not at Why,
report that and stop; do not guess which intent is meant.
The 8-step sequence
| Step | Action |
|---|---|
| 1 | Confirm the precondition above. |
| 2 | Read inputs in fixed order and build a ruling ledger: (a) ## Context and ### Decisions; (b) ## Insights newest-last, so a later ruling supersedes an earlier conflicting one; (c) resources/discovery--<slug>.md; (d) any other resources/*.md. |
| 3 | Decide the tier: adopt the brainstorming Tier: recommendation from Decisions or Insights; otherwise apply the PLASTIC.md tiers rubric (S = single mechanism or file cluster, M = one subsystem, L = cross-cutting or novel design). |
| 4 | Fill the template section by section, all 8 sections in template order. Read references/per-section-fill-rules.md now, filling the template is the trigger. Write the tier as the literal top line above # Spec:. Encode every ruling into its matching section, later supersedes earlier on conflict. A collapsed single-line S/M section is complete and valid; do not pad it. |
| 5 | Gap rule: if any section cannot be filled from the ledger built in step 2, STOP and ask the user for the missing ruling. Never invent scope to fill a gap. |
| 6 | State the gate position (below) so the user knows what happens next. |
| 7 | Self-verify against the checklist. Read references/self-verify-checklist.md now, verifying before presenting is the trigger. Fix any failing check, then re-verify from the top. |
| 8 | Present spec.md for the user-review gate, then hand off to plastic-intent-planning for How. |
What ships with it
3 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.
- 5d ago First seen · 74 lines · 171 tokens per session scan A f473343e2e95
plastic-intent-speccing is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed today), licensed MIT. It adds 171 tokens to every session and 1,115 once invoked, about $0.0009 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.