plastic-node-work

plastic-node-work is an agent for Claude Code from zalom/plastic. It costs 65 tokens per session (345 once invoked), scanned A, original, MIT.

A worker role in Plastic's node-graph runner, a system that breaks work into connected steps. It reads the assigned input, changes only the assigned worktree, commits the changes, and returns the specified YAML result.

In plain words
What is it for?
Use it for code changes assigned as one node in a larger workflow, including editing the named files, creating a commit, and reporting the outcome in YAML.
Why use it?
It gives an automated workflow a controlled implementation step with a clear file scope and machine-readable result. The runner, rather than the worker, checks the returned commit and result.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Part of the plastic plugin — 7 agents, 7 hooks, 1 MCP server shipped together

Good fit Use it for code changes assigned as one node in a larger workflow, including editing the named files, creating a commit, and reporting the outcome in YAML.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zalom/plastic/plastic-node-work
Install

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.

Clone the repo
git clone --depth 1 https://github.com/zalom/plastic

Made for: Claude Code.

Or install plastic, the plugin that ships this one along with the rest of its 7 agents, 7 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plastic-node-work

README.md
[![agentmods](https://agentmods.dev/badge/agents/zalom/plastic/plastic-node-work/github.svg)](https://agentmods.dev/agents/zalom/plastic/plastic-node-work)
Your own site
<a href="https://agentmods.dev/agents/zalom/plastic/plastic-node-work"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-node-work/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plastic-node-work

Your own site · 80×15
<a href="https://agentmods.dev/agents/zalom/plastic/plastic-node-work"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-node-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 345 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.00345
Opus 5.5 $0.00026 $0.00138
Sonnet 5.5 $0.00013 $0.00069
Haiku 4.5 $0.00006 $0.00034

Measured 7d ago against content hash d42b16c40454, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-30, from the pricing page.

Security

Grade A, and why

plastic-node-work scanned grade A with 1 finding 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 7d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

so `ruby -e File.write(...)` or a stray `curl` walks straight through it. The diff-scope check at
agents/plastic-node-work.md · 34 lines

What it actually says

You are one node in Plastic's node-graph runner: one node input in, your files and your commit and one YAML return out.

Read the node input the dispatch line names; it is your whole input. Make the changes it asks for, inside the worktree it names, and commit them there. Touch no file outside the node input's files: list, write to no other node's worktree, and write no ledger line yourself: the runner's own gates read your commit and your return, never your word.

This tools: allowlist is a guardrail on tool names, not a sandbox on what Bash can do once granted. A shell can read, write, and reach the network the same as any of the other tools here, so ruby -e File.write(...) or a stray curl walks straight through it. The diff-scope check at done is the real backstop for what your commit is allowed to touch, not this list.

End your turn with exactly one YAML document, the return the dispatch line names, nothing else around it.

Changes

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.

  1. 7d ago First seen · 34 lines · 65 tokens per session scan A d42b16c40454

Subscribe to this mod's changes

plastic-node-work is an agent published in the GitHub repository zalom/plastic (11 stars, last pushed 5d ago), licensed MIT. It adds 65 tokens to every session and 345 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.