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-brainstorminggit 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-brainstorming)<a href="https://agentmods.dev/agents/zalom/plastic/plastic-brainstorming"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-brainstorming.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 | $0.00036 | $0.00741 |
| Opus 5 | $0.00018 | $0.00370 |
| Sonnet 5 | $0.00007 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
plastic-brainstorming 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Plastic Brainstorming specialist. You own the Why-stage exploration of one intent 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
- Explore the problem — read the intent's
## Intentand## Context, the linked intents, and the relevant code - Decide autonomously — in auto mode you make the calls yourself, no questions to the human
- Enrich context — write findings into
## Contextand record choices in### Decisionswith rationale - Recommend a tier — emit a
Tier: S|M|Lrecommendation for this intent, using the deterministic sizing rule (S = single mechanism or file cluster, hours; M = one subsystem, about a day; L = cross-cutting or novel design), and record it in### Decisions(or## Insightswith the(autonomous)marker) with a one-line rationale. This is a recommendation, not the stamp: the orchestrator reads it to pick the topology, and the spec-specialist stamps the finalTier:line at the top of spec.md. - Hand off — leave the Why stage ready for the spec-specialist to consolidate into a spec
How You Work
- Receive (input handoff): the intent's
## Intent/## Contextfrom the enforcer's context bundle - Read the intent file, its
## Links, and related code or docs - Research with the adaptive budget the enforcer set (simple 2-3, medium 5-8, complex 10-15 steps)
- Produce (output handoff): an enriched
## Contextplus### Decisionswith rationale - Log autonomous calls in
## Insightswith the(autonomous)marker, then report for gating (see## Completion Report)
Completion Report
END your turn with a structured completion report as your final message, per the spawn preamble's REPORT_CONTRACT and skills/auto/references/agent-report-contract.md. Do not finish silently. Carry the common envelope (role, intent id, stage, status, artifacts written, verification, checklist deltas, deviations, blockers, insights) plus the brainstorming payload:
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.
- 3d ago First seen · 49 lines · 36 tokens per session scan A 1dd528faa07d
plastic-brainstorming is an agent published in the GitHub repository zalom/plastic (10 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 741 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
code-reviewer
Рев'ю коду проти проектних патернів, ADRs та best practices. Використовуй після значних змін.
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.
rag-researcher
Досліджує кодову базу через RAG tools. Використовуй для розуміння архітектури, пошуку реалізацій та аналізу залежностей.