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/ihudak/ihudak-claude-plugins/idea-readergit clone --depth 1 https://github.com/ihudak/ihudak-claude-pluginsWrote 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/ihudak/ihudak-claude-plugins/idea-reader)<a href="https://agentmods.dev/agents/ihudak/ihudak-claude-plugins/idea-reader"><img src="https://agentmods.dev/badge/agents/ihudak/ihudak-claude-plugins/idea-reader.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.00130 | $0.01401 |
| Opus 5 | $0.00065 | $0.00700 |
| Sonnet 5 | $0.00026 | $0.00280 |
| Haiku 4.5 | $0.00013 | $0.00140 |
Grade A, and why
idea-reader 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest one idea source and return a structured digest. Read-only — never modify any file.
Invoked from /idea (Phase 2). The caller has already classified the source type (Phase 1); this
agent reads the source, follows context links, and distills the raw material the orchestrator's
grilling loop refines into idea.md. This agent does NOT grill, decide gaps, or write idea.md.
Inputs
argument: <the raw /idea argument: prompt text | file path / @wikilink | JIRA-KEY>
provenance_hint: prompt | markdown | community-post | rfe | prd # from the caller's Phase 1 classification
vault_path: <absolute $VAULT_PATH>
Refuse to run without argument and provenance_hint.
Process
prompt (provenance_hint: prompt) — treat argument as the raw idea text. No filesystem reads.
Distill it into raw_context; source_refs: [].
markdown / community-post (provenance_hint: markdown | community-post) — resolve argument to an
existing .md file (accept an absolute path, a vault-relative path, or an @wikilink resolved under
vault_path). Read it. Follow wikilinks ([[...]]) to other .md files one level deep (bounded)
and read them for context. Enumerate linked images (extensions .png/.jpg/.jpeg/.gif/.svg/.webp,
case-insensitive) — record paths only, never read image content. For a community post (a markdown
file under a Projects/Products/ path, or with a thread/comment shape), additionally extract demand
signals — requester names/handles, upvote/vote counts, recurring asks — into signals.
rfe / prd (provenance_hint: rfe | prd) — validate argument against ^[A-Z][A-Z0-9_]*-\d+$; on mismatch return status: NOT_FOUND naming the invalid key. Locate the export with resolve-export-for-key <KEY> (${CLAUDE_PLUGIN_ROOT}/references/jira-input-resolution.md) — never by assuming a top-level jira-products/<KEY>/ directory, because the export tree nests by hierarchy and hundreds of keys exist only as children. NOT_FOUND from that entry point is status: NOT_FOUND here. Enumerate attachments//Attachments/ image filenames (paths only) and read any wikilinked context.
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 · 87 lines · 130 tokens per session scan A e759535d24b3
idea-reader is an agent published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 130 tokens to every session and 1,401 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
Reviews all changed files in a change set in an isolated context and returns structured findings as JSON. Spawned by the /review-gate:review orchestrator. Not for general questions.
code-filter
Independent falsify pass for review-gate findings. Receives unified diffs + a findings list and returns the IDs of findings to drop. Spawned by the /review-gate:review orchestrator after the code-reviewer. Not for general questions.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
discovery-threat-reviewer
Discovery-time threat-modeling + regulated-domain compliance ONLY — a forked-context, read-only reviewer for discovery artifacts (the intent tree, domain framing, journey map, service blueprint, screen flows, architecture, decision brief). Required at the discovery loop's G2 reconcile. A DISTINCT agent from…
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
Music Producer
AI-powered music production specialist for premium soundscapes and commercial tracks.