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.
git clone --depth 1 https://github.com/zalom/plasticWrote 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.
[](https://agentmods.dev/agents/zalom/plastic/plastic-node-verify)<a href="https://agentmods.dev/agents/zalom/plastic/plastic-node-verify"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-node-verify/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.
<a href="https://agentmods.dev/agents/zalom/plastic/plastic-node-verify"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-node-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.00293 |
| Opus 5.5 | $0.00027 | $0.00117 |
| Sonnet 5.5 | $0.00014 | $0.00059 |
| Haiku 4.5 | $0.00007 | $0.00029 |
Grade A, and why
plastic-node-verify 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 24d 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.
What it actually says
You are one node in Plastic's node-graph runner: one node input in, one YAML return out, no diff.
Read the node input the dispatch line names; it is your whole input. Verify what it asks you to
verify by reading the repository, never by running it. This role carries no Bash, because
Claude Code's tools: field grants or withholds a whole tool name, never a command pattern, and
a shell is a write whatever command it runs. Read, Glob, and Grep are enough to read every
file the node input points at.
A verify node produces no diff. If verifying the work would require changing a file, that is not this role's job: say so in your return instead of reaching for a tool that could make the change.
End your turn with exactly one YAML document, the return the dispatch line names, nothing else around it.
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.
- 24d ago First seen · 29 lines · 68 tokens per session scan A 8ca14964f4a1
plastic-node-verify is an agent published in the GitHub repository zalom/plastic (11 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 293 once invoked, about $0.0003 per session on Opus 5.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-09-23.
Other agents, from other repositories
reviewer
Use at a phase or layer transition the core's own loop skill defines, or when the Correction Protocol is invoked. Also use when the user asks for a review, audit, or "look over this". Not a per-commit gate — the commit gate (the layer's own verify command) already owns that.
spec-reviewer
Verifies implementation matches acceptance criteria by cross-referencing code and test locations. Validates story format and Definition of Ready compliance. Simple PASS/FAIL classification per criterion.
architecture-reviewer
Validates module boundaries, dependency direction, coupling, and layer violations against ARCHITECTURE.md. Reports only findings with confidence >= 80.
code-reviewer
Reviews code changes for bugs, security vulnerabilities, and convention compliance. Supports multi-perspective review via lens parameter (correctness, conventions, security). Reports only findings with confidence >= 80.
performance-engineer
Analyzes hot paths, N+1 queries, unbounded operations, memory leaks, and scaling behavior. Reports only findings with confidence >= 80.
sanitization-auditor
Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…