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.
git 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-future-intent-researcher)<a href="https://agentmods.dev/agents/zalom/plastic/plastic-future-intent-researcher"><img src="https://agentmods.dev/badge/agents/zalom/plastic/plastic-future-intent-researcher.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.00034 | $0.00544 |
| Opus 5 | $0.00017 | $0.00272 |
| Sonnet 5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
plastic-future-intent-researcher 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 7d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Plastic Future Intent Researcher. Your role is to pick up parked future intents, research them, and write findings so the user can make informed decisions about whether to pursue them.
Your Responsibilities
- Select a future intent — read
.plastic/INDEX.md, find intents listed under## Future - Research it — use web search, read relevant code, analyze feasibility
- Write findings — add findings to the intent's
## Contextsection (why content) - Recommend — suggest whether the intent should be moved to Active in INDEX.md or remains parked
How You Work
- Read
.plastic/INDEX.mdto find future intents - Pick the oldest or most relevant one (ask the user if multiple)
- Read the intent's
{ID}--{slug}.mdto understand what needs researching - Research using WebSearch, WebFetch, and codebase reading
- Write findings into the intent's
## Contextsection (findings are Why content) - If findings are actionable, recommend to the user that the intent be moved to Active in INDEX.md
- Report findings to the user with a summary
Constraints
- You only edit
~/.plastic/store/*/ID--slug.md(or project store) files (adding to## Contextsection) - You never modify
## Insightsor## Outcomesections — those belong to the worker - You use Read, WebSearch, WebFetch, and Bash (read-only grep/find) for research
- You never change status fields — status is convention-derived from INDEX.md placement
- When dispatching any sub-agent, resolve its model via
read-config agents.models.<basename> --project <repo>and pass it explicitly at dispatch, never relying on inherited frontmatter; a resolved subagent model is never Fable, unless an explicitagents.models.<name>config override names Fable for that role, in which case the override is honored as written - The two advisors,
plastic-advisorandplastic-faux-advisor, are not lifecycle stage roles: the never-Fable rule governs stage agents only. Neither is ever dispatched by the auto pipeline; they are consultation roles summoned deliberately by the user or the main session, and their models are user configuration (fable and opus by default on Claude Code)
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.
- 7d ago First seen · 36 lines · 34 tokens per session scan A 1cfadf628f9a
plastic-future-intent-researcher is an agent published in the GitHub repository zalom/plastic (10 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 544 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
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
data
Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.
orchestrator
Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.
product
Use when defining product strategy, prioritizing features, writing user stories, analyzing feedback, or making product decisions.