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/project-continuingnpx skills add zalom/plastic --skill project-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.00100 | $0.01598 |
| Opus 5 | $0.00050 | $0.00799 |
| Sonnet 5 | $0.00020 | $0.00320 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
plastic-project-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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Continuing - land on the board
plastic-project-continuing is the project route of plastic-continuing. It lands on the
Markdown board, presents active work and the most-valuable next work, and stops. It does not
resume a specific intent by ledger (that is plastic-intent-continuing) and it asks nothing.
Continue (present the board)
Land on the Markdown board via the plastic-dashboard skill. Rendering belongs there, not
here - run the data payload and fill + present the matching template:
- Project loaded ->
ruby ~/.plastic/scripts/dashboard.rb project <slug> --data - Otherwise (no project loaded, the global fallback) ->
ruby ~/.plastic/scripts/dashboard.rb continue --data
Fill the matching template from plastic-dashboard's templates/ and present the filled
Markdown in your reply (every time, non-optional). If the reply does not contain the filled
Markdown, the user sees nothing - tool-call stdout and hook additionalContext are both
invisible to them. hook-continue also emits a one-line systemMessage summary as a
hook-owned fallback; treat it as a floor only, never as a substitute for presenting the full
board here. See plastic-dashboard for the fill mechanics (references/board-fill.md has the
scoped detail).
The board load runs the scoped store check on every load (doctor --store <scope>): the
global board runs --store global and a project board runs --store <slug>. The result
arrives in the payload as store_health; surface it as a one-line store-health note. It is
non-fatal (a warn or fail is shown as data, it does not block continuing).
Priority Order
- Active intents first - surface work in progress.
- Project context - if in a registered project, show governing + tactical intents.
- Stale future intents - surface for triage (see below).
- Fresh future intents - offer as next work.
Stale Future Intents
If a future intent's created date is older than the configured stale_threshold_days
(default 3), surface it for triage without taking action:
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 · 120 lines · 100 tokens per session scan A 36d4f50172b9
plastic-project-continuing is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 1,598 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.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
ss-component
Generate a new UI component following the StyleSeed design conventions.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.