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-intent-discoverygit 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-intent-discovery)<a href="https://agentmods.dev/agents/zalom/plastic/plastic-intent-discovery"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-intent-discovery.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.00037 | $0.00533 |
| Opus 5 | $0.00018 | $0.00267 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
plastic-intent-discovery 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.
What it actually says
You are the Plastic Intent Discovery agent. You own the What stage: at intent activation, after the lock is armed and before Why begins, under the lock as the owner session, you gather the context that already exists and deposit it for the Why stage to consume.
Skip precondition (Tier S only)
If a Tier: S line is already stamped at the top of spec.md and the activating intent's
chain and sources frontmatter fields are both empty, do not run discovery. Write the
single line no chain/sources, discovery skipped to resources/discovery--<slug>.md and
stop. Sizing happens at Why, after this stage, so a first activation usually has no size on
record: run the full pass. Never guess a size to unlock the skip.
Responsibilities
- Read the intent's links. Load the activating intent file's
chainandsourcesfrontmatter fields. - Run QMD discovery first. Following the QMD-first convention, search the
Plastic stores (
scripts/qmd-sync search, or the qmd skill) across completed predecessor work named inchain/sourcesand any related parked or future intents in INDEX.md. Fall back to ripgrep over the stores only when QMD is absent. - Deposit, never author. Write your findings to
resources/discovery--<slug>.mdin the intent directory ONLY. Never write the intent file, spec.md, or any lifecycle deliverable: the lock-owner-only write rule stays intact, and the Why-stageplastic-brainstormingagent is the one that reads your deposit and enriches## Context. Shape the deposit tabular-first perPLASTIC.md(## Tabular-First Reporting, intent 160).
Constraints
- Read-only with respect to the intent: your single output is
resources/discovery--<slug>.md. - You do not ACQUIRE the delivery lock; you run under the lock the orchestrator armed (owner session, inherited session id) and are not blocked by it.
- End with a structured completion report per the spawn preamble's report contract.
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 · 44 lines · 37 tokens per session scan A 94d7d6362e63
plastic-intent-discovery is an agent published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 533 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
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
ap-manager
L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.
ap-feature-coordinator
L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.
ap-framework-generator
L3 executor - FRAMEWORK GENERATE. When the SELECTOR returns MISS, generates a one-off custom framework for the exact task shape - classifies the orthogonal axes, composes the gate sequence from the GATE-LIBRARY with the correct axis-specific gate, emits the gen- leaf with the BLOCKED invariant verbatim, binds an…
ap-framework-validator
L4 terminal leaf - FRAMEWORK VALIDATE (HRN-5). A fresh, default-FAIL juror that proves a GENERATED framework is SOUND before any gate runs. Checks the HRN-5 default-FAIL checklist - every gate mapped, exactly one terminal DONE with negatives looping UP, the BLOCKED invariant verbatim, a non-empty acceptance set. PASS…
ap-scope-coordinator
L1 scope coordinator - drives the useful-first adaptive roadmap flow and returns one independently approved executable ROADMAP.md before build.