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-executingnpx skills add zalom/plastic --skill intent-executinggit 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.00087 | $0.02654 |
| Opus 5 | $0.00044 | $0.01327 |
| Sonnet 5 | $0.00017 | $0.00531 |
| Haiku 4.5 | $0.00009 | $0.00265 |
Grade A, and why
plastic-intent-executing 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing a Plan
Overview
Load plan from the active intent's plan.md, execute all tasks, review per the tier gate below, report when complete.
Step 0: Sync Worktree First
Before Step 1 (Load Plan) in either workflow below, sync the code worktree with main first, so no edit lands on a path a merged rename or delete already removed:
git -C <worktree> fetch origin && git -C <worktree> merge --ff-only origin/main
After syncing, verify the plan's target files exist at the paths plan.md names. If a named file or directory is missing (renamed or removed upstream), stop and report it rather than editing a stale path.
Read ../plastic-conventions/references/locks-and-worktrees.md for delivery isolation: the
single-owner lock, claims, worktrees, solo mode, and the station ledger, before touching the
worktree above. This path resolves relative to this skill's own installed directory.
Mode Selection
Check for superpowers first
If superpowers:subagent-driven-development is available as a skill, delegate to it. If only superpowers:executing-plans is available, delegate to that. If neither is available, use Plastic's own execution engine below.
CRITICAL: when delegating to superpowers:
- Tell the skill that the plan is at
~/.plastic/store/ID--slug/plan.md(notdocs/superpowers/plans/) - Tell the skill that specs live at
~/.plastic/store/ID--slug/spec.md(notdocs/superpowers/specs/) - All meta-artifacts must stay inside
~/.plastic/store/ID--slug/ - Code files go in the project tree as normal
- Superpowers skills respect "user preferences for plan/spec location"; Plastic IS that preference
Subagent-Driven (Default)
Dispatches subagents to do the work. The controller never implements. It dispatches, reviews, and tracks progress. How many dispatches it makes depends on the tier stamped at the top of spec.md (the Tier: line, the single authoritative record). plan.md carries a bold **Tier:** field copied from it, a convenience only:
What ships with it
4 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 · 202 lines · 87 tokens per session scan A 935c96aff969
plastic-intent-executing is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 2,654 once invoked, about $0.0004 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 一起使用。.