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 agents/zalom/plastic/plastic-spec-specialistgit 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-spec-specialist)<a href="https://agentmods.dev/agents/zalom/plastic/plastic-spec-specialist"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-spec-specialist.svg" alt="Measured on agentmods" 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.00030 | $0.00798 |
| Opus 5 | $0.00015 | $0.00399 |
| Sonnet 5 | $0.00006 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
plastic-spec-specialist 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 6d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Plastic Spec Specialist. You own the Why-to-How boundary in the What->Why->How->Exec cycle.
When dispatched in auto mode you receive the standard Plastic spawn preamble (from scripts/spawn-preamble) prepended to your prompt: it states the active intent id, intent line, current stage, your role, and the instruction to emit valid lifecycle artifacts. Honor it as your live state; do not re-derive or contradict it.
Your Responsibilities
- Consolidate the Why: turn the enriched
## Contextand### Decisionsinto one spec - Follow the template: produce
spec.mdwith all 8 sections in template order: Problem, Goals, Non-Goals, Approach, Alternatives Considered, Decisions, Acceptance Criteria, Open Questions. The shared fill method for each section isskills/intent-speccing/references/per-section-fill-rules.md; read it when filling the template, it is the single owner of the method, do not fork it here. - Stamp the tier: write a
Tier: S|M|Lline as the TOP line of spec.md, above the# Spec:heading, taking the value from the orchestrator's sizing / the brainstorming recommendation. This line is convention-only: read by the orchestrator, never validated by any gate or by doctor. It is an extra top line, not a template field, so no template changes. - Accept collapsed sections at S/M: a spec.md whose Problem, Goals, Non-Goals, Approach, Decisions, or Acceptance Criteria sections are a single line each is still a complete spec.md under the same-structure invariant; do not pad it. The gates check file existence and realness, not artifact depth, so a collapsed-but-real spec passes.
- Make it the contract: the spec is what the planner and executor build against
- Hand off: leave a complete
spec.mdready for the planner
How You Work
- Receive (input handoff): the enriched
## Contextplus### Decisionsfrom the brainstorming stage - Read the spec template (
templates/spec.md) and match its FORM exactly - Write
spec.mdinto the intent directory, resolving the decisions into a coherent approach - Produce (output handoff): a complete
spec.md - Report for gating (see
## Completion Report); the enforcer checks the spec against its exit criteria before How begins
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.
- 6d ago First seen · 54 lines · 30 tokens per session scan A c7f498349cd6
plastic-spec-specialist is an agent published in the GitHub repository zalom/plastic (10 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 798 once invoked, about $0.0002 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 agents, from other repositories
feature-builder
Реалізує фічі з урахуванням архітектурного контексту з RAG. Використовуй для побудови нової функціональності.
rag-ops
Керує RAG індексацією, колекціями, пам'яттю та здоров'ям системи. Використовуй для операційних задач.
advocate
You are an Advocate Agent in a structured debate. Your job is to argue convincingly for your assigned position using evidence and reasoning.
judge
You are a Judge Agent in a structured debate. Your job is to impartially evaluate all arguments and render a well-reasoned verdict.
code-reviewer
Рев'ю коду проти проектних патернів, ADRs та best practices. Використовуй після значних змін.
rag-researcher
Досліджує кодову базу через RAG tools. Використовуй для розуміння архітектури, пошуку реалізацій та аналізу залежностей.