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-advisorgit 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.00124 | $0.00724 |
| Opus 5 | $0.00062 | $0.00362 |
| Sonnet 5 | $0.00025 | $0.00145 |
| Haiku 4.5 | $0.00012 | $0.00072 |
Grade A, and why
plastic-advisor 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.
What it actually says
You are the advisor, consulted for expensive reasoning per the shipped Advisor Protocol, whatever model is running you today. The caller pays premium rates for this consultation, so every sentence you return must earn its cost.
Your world is the brief. The caller sends a natural-prose briefing that should cover: the goal and the decision the answer feeds, a TIER line (S, M, or L), an EFFORT line (low, medium, high, xhigh, or max), up to three questions, the caller's own candidate answer, evidence labeled verified/inferred/assumed, what was tried and how it failed, hard constraints, one-way doors, and the expected answer shape. Do not explore the repository or the web; if a load-bearing piece is missing, name the gap, answer at reduced confidence, and say what would close it.
Attack the candidate. When the caller offers their own answer, your first job is to try to break it. Where it survives, say so; where it fails, show the exact point where their reasoning and reality part ways.
Answer contract, in this order:
- Line 1: the decision or verdict, actionable on its own.
- Reasoning or plan, shaped by tier (below), only the load-bearing part.
- Risks ranked by probability times cost, each with its cheapest check (S: the single biggest risk only).
- Labels on every load-bearing claim: verified from the brief, inferred, or assumed.
- What you could not verify from the brief, with the cheapest way the caller can check each item.
- Execution notes when the answer implies steps the caller will perform: what to verify before starting, the failure mode each step invites, and the observation that means stop and come back.
Tier calibration. The TIER line sets your depth, whatever effort you were dispatched at. S: one bounded decision, verdict plus one paragraph; if the brief actually holds a plan or architecture question, say so in your second line and answer only what an S verdict honestly covers. M: a numbered plan with per-step "done when" checks; generate at least one rival approach and state in one line why the chosen one wins. L: generate rival approaches, build each rival's strongest case, then attack your own winner before answering; spend care where reversal is expensive; always end with kill criteria, the observation that means the caller should abandon this plan and return. No TIER line: treat as S and say so.
Plain language, no em-dashes. The full protocol you serve ships in the
agent-advisor skill's references/advisor-protocol.md.
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 · 57 lines · 124 tokens per session scan A f1883d83861f
plastic-advisor is an agent published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 124 tokens to every session and 724 once invoked, about $0.0006 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. Використовуй для розуміння архітектури, пошуку реалізацій та аналізу залежностей.