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 skills/zalom/plastic/agent-advisornpx skills add zalom/plastic --skill agent-advisorgit 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/skills/zalom/plastic/agent-advisor)<a href="https://agentmods.dev/skills/zalom/plastic/agent-advisor"><img src="https://agentmods.dev/badge/skills/zalom/plastic/agent-advisor.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.00104 | $0.01127 |
| Opus 5 | $0.00052 | $0.00563 |
| Sonnet 5 | $0.00021 | $0.00225 |
| Haiku 4.5 | $0.00010 | $0.00113 |
Grade A, and why
plastic-agent-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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Advisor
Plastic ships two consultation agents, never dispatched by the auto pipeline, summoned only when you decide the reasoning is worth buying:
plastic-advisor("the real advisor"): the frontier model itself, expensive, billed through usage credits. Spawn it for a few rounds on the hardest problem, then close the session.plastic-faux-advisor("the imitation advisor"): an ordinary model carrying the same reasoning discipline inline in its own body, so it reasons the same disciplined way at a fraction of the cost. The cheaper default.
When to consult (and when not to)
Buy a consultation for: decisions with one-way doors (architecture, migration order, public contracts); turning a goal plus evidence into a step plan with checks; adversarial review of your plan or conclusion before an irreversible step; a deadlock after two failed attempts where you cannot say why; ranking several plausible options when the ordering decides where you spend the next day.
Never buy a consultation for: anything a tool can answer (search, reading code, running
tests, documentation), writing code at volume, confirming a decision you already made,
style or naming a linter would settle, or anything reversible and cheap you have not
tried first. The full buy/never-buy list, the tier table, and the entry test live in
references/advisor-protocol.md; read it before writing a brief for the first time in
a session.
Routing: which advisor answers
- Read the harness-scoped config:
advisor.claude.default, the only advisor routing key the installer writes. If unset, useplastic-advisor, the shipped default. - If the user names which advisor they want ("ask the real one", "use Fable", "ask the
cheap one"), honor that directly and dispatch
plastic-advisor(the real advisor) orplastic-faux-advisor(the cheaper imitation) accordingly, overriding step 1 for this consultation only. - If
advisor.enabledreadsfalse, neither advisor agent nor this skill is installed; this step should not be reachable, but if it is, tell the user the advisor is disabled and point at "Setting the default" below. - Dispatch the resolved agent with a brief built per
references/advisor-protocol.mdsection 4 (natural prose, the block is a completeness check, not a form to fill). State TIER (S, M, or L) and EFFORT explicitly; classify low and prove your way up, never open high "to be safe". - Consume the answer per the protocol's section 5: run the Operating Manual's five-question self-test on the advisor's plan before executing it. Advice is input, not authority; the plan is the advisor's, the outcome is yours.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 93 lines · 104 tokens per session scan A 476eb24a1587
plastic-agent-advisor is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 104 tokens to every session and 1,127 once invoked, about $0.0005 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 skills, from other repositories
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
agent-spec-tool-first
CRITICAL: Use for agent-spec CLI tool workflow. Triggers on: agent-spec, contract, lifecycle, guard, verify, explain, stamp, checkpoint, plan, requirements, work-units, knowledge requirements, KLL, docs vs knowledge, spec verification, task contract, spec quality, lint spec, run log, "how to verify", "how to use…
agent-spec-authoring
CRITICAL: Use for writing and editing agent-spec .spec/.spec.md files. Triggers on: write spec, create spec, edit spec, new spec, spec authoring, task contract, .spec file, .spec.md file, BDD scenario, acceptance criteria, completion criteria, test selector, boundary, constraint, intent, decision, out of scope, "how…
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.