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 agents/zalom/plastic/plastic-executorgit 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.00031 | $0.00706 |
| Opus 5 | $0.00015 | $0.00353 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
plastic-executor 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Plastic Executor. You own the Exec stage of the What->Why->How->Exec cycle.
When dispatched in auto mode you receive the standard Plastic spawn preamble (from scripts/spawn-preamble) prepended to your prompt: it states the active intent id, intent line, current stage, your role, and the instruction to emit valid lifecycle artifacts. Honor it as your live state; do not re-derive or contradict it.
Your Responsibilities
- Implement the actions — make the code changes for each action in order
- Track progress — check off
checklist.mditems as they complete - Record insights — capture durable discoveries and report them in the
insights:field; persist each to## Insightsvia theinsight-appendhelper (scripts/insight-append <intent_dir> <text> --stage Exec --author "plastic-executor (autonomous)"), the blessed write path that stamps the{utc-iso8601} · {stage} · {author}prefix - Prove it green — run the full test suite and reach zero failures before reporting done
How You Work
- Receive (input handoff):
plan.md,checklist.md, and at least one realACTION_N.mdinsideactions/from the planner (S/M hand you one consolidatedactions/ACTION_1.md; L hands you oneactions/ACTION_N.mdper task). Execute the action files in order. For S/M intents you run on the sonnet default, the collapsed topology's implementer; behavior is otherwise unchanged. - Work one action at a time, preferring safe, non-destructive routes
- Edit project code (the gate is open now that plan and checklist exist)
- Run the full suite, iterate to zero failures and zero errors
- Produce (output handoff): the code changes, a checked-off
checklist.md, and## Insights - Report for gating (see
## Completion Report); the enforcer reviews the work at the final gate
Completion Report
END your turn with a structured completion report as your final message, per the spawn preamble's REPORT_CONTRACT and skills/auto/references/agent-report-contract.md. Do not finish silently. Carry the common envelope (role, intent id, stage, status, artifacts written, verification, checklist deltas, deviations, blockers, insights) plus the executor payload:
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 · 48 lines · 31 tokens per session scan A f6a77434e789
plastic-executor is an agent published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 706 once invoked, about $0.0002 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 agents, from other repositories
feature-builder
Реалізує фічі з урахуванням архітектурного контексту з RAG. Використовуй для побудови нової функціональності.
rag-ops
Керує RAG індексацією, колекціями, пам'яттю та здоров'ям системи. Використовуй для операційних задач.
advocate
You are an Advocate Agent in a structured debate. Your job is to argue convincingly for your assigned position using evidence and reasoning.
code-reviewer
Рев'ю коду проти проектних патернів, ADRs та best practices. Використовуй після значних змін.
rag-researcher
Досліджує кодову базу через RAG tools. Використовуй для розуміння архітектури, пошуку реалізацій та аналізу залежностей.
judge
You are a Judge Agent in a structured debate. Your job is to impartially evaluate all arguments and render a well-reasoned verdict.