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/roadmapnpx skills add zalom/plastic --skill roadmapgit 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.00074 | $0.01028 |
| Opus 5 | $0.00037 | $0.00514 |
| Sonnet 5 | $0.00015 | $0.00206 |
| Haiku 4.5 | $0.00007 | $0.00103 |
Grade A, and why
plastic-roadmap 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap
A roadmap is a named, ordered, delivery-side collection of intents: the delivery-side counterpart
to a release (completion-side, CHANGELOG.md). It lives at roadmaps/{slug}.md, a sibling of
INDEX.md wherever INDEX.md lives: the global tier's ~/.plastic/roadmaps/ (beside
~/.plastic/INDEX.md), or a project's root, ~/.plastic/projects/{slug}/roadmaps/ (beside that
project's INDEX.md and project.yml). It never sits inside store/, which holds intent
directories, not project artifacts.
A roadmap file has four parts: a title/meta header, ## Goal (prose), ## Batches (ordered;
entries inside a batch are parallel-safe, batches run sequentially), and an append-only dated
## Log. A roadmap written before owner ruling 145 may instead use the legacy ## Waves heading;
reading accepts both, but every new roadmap is scaffolded with ## Batches, and an existing
roadmap file's heading is never renamed to migrate it. Each batch entry mirrors that intent's
status in INDEX.md (queued/delivering/delivered/abandoned/blocked).
INDEX.md is the single writer of intent status; on any conflict INDEX wins and the roadmap
entry is corrected to match.
The skill operates on the roadmap file directly via Read/Edit. The one deterministic helper it
uses is the savepoint ledger writer (scripts/roadmap-savepoint, append/rebuild); every verb's
closing step calls append after its Read/Edit, and the roadmap .md file itself stays
Read/Edit-only.
Verbs
| Verb | When | Mechanics |
|---|---|---|
| Create | user wants to start a new roadmap / plan a delivery batch | references/operations.md#create |
| Add / reorder entries | user wants to add intents to a batch or resequence batches | references/operations.md#add--reorder-entries |
| Sync status mirror | an entry's status may be stale against INDEX | references/operations.md#sync-status-mirror |
| Append log line | a roadmap event just happened (created, batch done, closed) | references/operations.md#append-a-log-line |
| Read / consume | a human or a coordinator needs the roadmap's current state | references/operations.md#read--consume |
| Close / archive | the roadmap's ## Goal is reached |
references/operations.md#close--archive |
What ships with it
2 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 · 65 lines · 74 tokens per session scan A eb1ac614cdde
plastic-roadmap is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 1,028 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
batch-all-issues
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the goal-pr skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
resolve-scrap-issues
Fetch recent maintainer-scrap issues, validate each with web research, then either close the ones that need no action or open a single consolidated pull request that resolves the ones that do.
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.