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/roadmap-continuingnpx skills add zalom/plastic --skill roadmap-continuinggit 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.00098 | $0.01169 |
| Opus 5 | $0.00049 | $0.00584 |
| Sonnet 5 | $0.00020 | $0.00234 |
| Haiku 4.5 | $0.00010 | $0.00117 |
Grade A, and why
plastic-roadmap-continuing 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Continuing - resume the mid-flight roadmap
plastic-roadmap-continuing is the roadmap route of plastic-continuing. It finds the tier's
mid-flight roadmap, presents its state, then asks the user how to proceed, exactly once.
Before intent 158a1 there was no automated way to do this: the 171 (consistency-dividend)
roadmap handoff had to be resumed by hand, carried as a free-prose note in 171's own
## Insights. This skill closes that gap.
Find the mid-flight roadmap
-
Determine the tier (project vs. global) and enumerate that tier's live
roadmaps/*.md(excluderoadmaps/archived/). Read via Read/glob, orplastic-roadmap's Read/consume verb. Seeplastic-roadmap'sreferences/file-format.mdfor the file grammar; do not duplicate it here. -
For each candidate, also read its paired ledger
roadmaps/<slug>.savepoint.mdwhen present (seeplastic-roadmap'sreferences/file-format.md#savepoint-ledger): its last line(s) are a cheaper, precise last-event signal (for exampledispatched 134ormerged 172), read alongside the existing## Batches(or legacy## Waves) /## Logjudgment. The ledger is read-only here, a derived signal, never a new status field; INDEX.md stays the sole status writer. -
Rank liveness by calling the shared reader in which mode (one implementation across the auto loop and this skill):
ruby ~/.plastic/scripts/roadmap-next --roadmaps-dir <tier>/roadmaps --whichRead
stateand the winningroadmap. Whenstateistie,tie_candidateslists the equally-live roadmaps to present side by side; the single "auto or guided?" ask below doubles as the resolution.roadmap-nextliveness-ranks the same way this skill used to do by eye (adeliveringorblockedentry wins, else the newest ledger or## Logtimestamp), now deterministically. Seereferences/liveness-ranking.mdfor the algorithm it implements. -
A genuine tie (two candidates equally live) is presented to the user and resolved by the single ask below, not silently picked.
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 · 90 lines · 98 tokens per session scan A 28a17616bc09
plastic-roadmap-continuing is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 1,169 once invoked, about $0.0005 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 一起使用。.