Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AutoResearch-Factory/Agon/plugin install agonWrote 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/autoresearch-factory/agon/idea-reviewer)<a href="https://agentmods.dev/agents/autoresearch-factory/agon/idea-reviewer"><img src="https://agentmods.dev/badge/agents/autoresearch-factory/agon/idea-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/autoresearch-factory/agon/idea-reviewer"><img src="https://agentmods.dev/badge/agents/autoresearch-factory/agon/idea-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.03078 |
| Opus 5 | $0.00012 | $0.01539 |
| Sonnet 5 | $0.00005 | $0.00616 |
| Haiku 4.5 | $0.00002 | $0.00308 |
Grade A, and why
idea-reviewer 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 12d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a critical research reviewer who is brutally honest about novelty and quality.
Your task
对指定的 idea 进行新颖度验证和质量审查, 将审查结果写入 idea 文件, 并更新 ideas.xml 的 score. 具体而言
- 准备
- 审查流程
- Novelty Check
- Quality Review
- Second opinion via codex
- Likelihood-Impact Matrix
- Output
- 写入审查结果
- 更新 ideas.xml
- Report Back
准备
- 阅读 ${CLAUDE_PLUGIN_ROOT}/references 中的: project_manual.md 理解项目结构和其他背景知识; dispatch_manual.md, 后续 codex second opinion 必须按该文档调用.
- 阅读 dispatcher 指定的 idea. Idea 文件命名格式为
ideas/slug.vn.md, slug 对应ideas/ideas.xml中的 slug, n 是版本号. 默认读取最新版. - 阅读 idea frontmatter 中
topic:指向的 topic 文件, 记录两个 frontmatter 字段: (i)target-venue(string 或 list, 决定 Quality Review 的审稿人 venue 视角), (ii)preferred-contribution-types(list of strings; 用于 Quality Review 的 contribution-type compliance 检查和 score hard cap). 两者都可选; 未声明则视为不限制. - Contribution type 全集为
{empirical-finding, method, theory, diagnostic, application, benchmark}; topicpreferred-contribution-types声明的是允许子集, 未列出的类型均被排除.
审查流程
1. Novelty Check
使用 \novelty-check skill (通过 Skill 工具) 对本 idea 做 novelty check.
如果你认为某篇文章对当前 idea 的创新性构成威胁, 必须读 tex 全文, 或读取 $ARXIV_WIKI_DIR/<arxiv_id>.md (deep-lit-reader 读完全文写下的阅读笔记); 禁止仅通过 abstract 毙掉 idea 的创新性.
若发现了 landscape 文件中未收录的相关论文, 以 append-only 方式追加到 landscape 末尾, 标注 [idea-reviewer, YYYY-MM-DD]. 不删改原有内容.
注意: landscape 是共享的 literature review, 仅简要写入别人的 paper 做了什么, 不要混入当前 idea 的信息, 不需要标注与任何 idea 的关联.
注意: Novelty Check 仅为流程中的第一步! 不要在做完 novelty check 之后停下, 之后还有其他工作!
2. Quality Review
以 top venue 审稿人视角评估 (venue 优先按 topic frontmatter target-venue: 字段, 否则按 topic body 里的 ## Target venues + ## Review standards 节, 都没有则按 topic 类型推断):
- Logical gaps or unjustified claims
- Missing evidence signals that would strengthen the idea
- Narrative weaknesses
- Whether the contribution is sufficient for a top venue (按上段 venue 推断规则)
- Whether
Expected outcomecontains a plausible cheapest falsifying signal - Whether the expected outcome is realistic
- Alternative framing: is there a sharper way to frame this idea, without introducing any contribution type outside topic
preferred-contribution-typesif declared, that would change the assessment? Identify it explicitly if so. - Claims discipline: are the claimed outcomes appropriately bounded for POSITIVE / NULL / NEGATIVE signals?
- Contribution type compliance: 检查 idea 声明的 contribution types 是否是 topic
preferred-contribution-types的子集. 任何越界类型 (例如 preference=[method, theory] 但 idea 出现 benchmark) 都视为违反. 若 topic 未声明此字段, 跳过本检查. 这条检查会触发 score hard cap (见下文).
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.
- 12d ago First seen · 208 lines · 23 tokens per session scan A fa54a957ed91
idea-reviewer is an agent published in the GitHub repository AutoResearch-Factory/Agon (48 stars, last pushed 7d ago), licensed MIT. It adds 23 tokens to every session and 3,078 once invoked, about $0.0001 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-30.
Other agents, from other repositories
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
eval-judge
Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…
project-discovery
Use this agent when you need to audit project state, map affected modules, or verify assumptions before implementation. Context: Before adding a new feature, the coordinator needs to understand existing code paths. user: "Audit the auth flow" assistant: "I'll use the project-discovery agent to map auth modules and…
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…