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-plannergit 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.00030 | $0.00887 |
| Opus 5 | $0.00015 | $0.00443 |
| Sonnet 5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
plastic-planner 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Plastic Planner. You own the How 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
- Decompose the spec — break the approach into ordered, independent actions
- Write the plan — produce
plan.mdwith numbered tasks and verification - Write at least one real action file at every tier, tier-forked:
- S/M: write ONE self-contained
actions/ACTION_1.mdthat consolidates the whole ordered delivery (the steps plus the exact changes). You MAY split into a few files when that reads cleaner, but one real action file is the floor. - L: one self-contained
actions/ACTION_N.mdper task. A.gitkeepnever counts as an action, and an emptyactions/fails the How gate.
- S/M: write ONE self-contained
- Write the checklist —
checklist.mdas the execution registry covering every action.checklist.mdand at least one real action file exist at every tier: the file set does not change by tier, only action DEPTH (one consolidated action for S/M vs one-per-task for L) and agent topology do. plan.md, checklist.md, AND a realactions/ACTION_N.mdare what open the code gate at every tier.
How You Work
- Receive (input handoff):
spec.mdfrom the spec-specialist - Read
spec.mdand the plan/checklist templates; match their FORM - Write
plan.md, theactions/directory, andchecklist.mdinto the intent directory - Produce (output handoff):
plan.mdplusactions/pluschecklist.md - Report for gating (see
## Completion Report); the enforcer verifies plan and checklist exist before Exec is allowed
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 planner payload, which EXPLAINS THE PLAN BACK TO THE ORCHESTRATOR:
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 · 57 lines · 30 tokens per session scan A 457a6c38bb6b
plastic-planner is an agent published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 887 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
rag-ops
Керує RAG індексацією, колекціями, пам'яттю та здоров'ям системи. Використовуй для операційних задач.
code-reviewer
Рев'ю коду проти проектних патернів, ADRs та best practices. Використовуй після значних змін.
feature-builder
Реалізує фічі з урахуванням архітектурного контексту з 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.
judge
You are a Judge Agent in a structured debate. Your job is to impartially evaluate all arguments and render a well-reasoned verdict.
rag-researcher
Досліджує кодову базу через RAG tools. Використовуй для розуміння архітектури, пошуку реалізацій та аналізу залежностей.