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-creatingnpx skills add zalom/plastic --skill intent-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.00063 | $0.02155 |
| Opus 5 | $0.00032 | $0.01077 |
| Sonnet 5 | $0.00013 | $0.00431 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
plastic-intent-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 2d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating an Intent
When to Use
- User starts new work ("build X", "fix Y", "research Z")
- No active intent matches the current task
- User explicitly says "new intent" or "create intent"
- An agent discovers work needed during implementation
Determine Tier
Global intent (strategic): created when working outside a registered project, or when the user expresses a high-level goal. Stored in ~/.plastic/store/.
Project intent (tactical): created when working inside a registered project directory. Stored in ~/.plastic/projects/{slug}/store/. Automatically linked to the project's governing intent.
Detection logic:
- Read
~/.plastic/projects.yml - CWD match: Match CWD against registered project paths
- If CWD is inside a registered project → project intent (tactical)
- Explicit mention: User mentions an existing project by name ("add this to reddit-kb", "new intent for plastic")
- Look up project in
projects.ymlby slug - If found → project intent (tactical) in that project's store at
~/.plastic/projects/{slug}/store/ - Agent changes working directory to the project path for execution
- Look up project in
- No match: CWD is not in a project AND no project mentioned
- → global intent (strategic) in
~/.plastic/store/
- → global intent (strategic) in
When creating a tactical intent in a project store:
- Read the project's
AGENTS.mdfor project context and decisions - Link back to the project's governing intent (from
projects.ymlparentfield) viasources(the project genuinely is formed from its founding intent, a true formative edge, reciprocated on the founding intent'schain) - Add
[[global:<parent_ID>]]backlink in## Links - The intent's Folgezettel ID is scoped to the project store (run
folgezettel-idagainst the project's store at~/.plastic/projects/{slug}/store/)
Workflow
1. Determine Store Location
- Global:
~/.plastic/store/ - Project:
~/.plastic/projects/{slug}/store/
2. Check for a Duplicate or Predecessor (QMD-first)
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.
- 2d ago First seen · 165 lines · 63 tokens per session scan A 449f1bcdde0b
plastic-intent-creating is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 2,155 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.
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.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.