proposal-reviewer

proposal-reviewer is an agent for Claude Code from AutoResearch-Factory/Agon. It costs 22 tokens per session (1,609 once invoked), scanned A, original, MIT.

A research-paper proposal reviewer that checks whether a planned study is focused, practical, and supported by a clear paper structure.

In plain words
What is it for?
Reviewing proposal files, writing review comments, and recording a score in the project’s proposal list.
Why use it?
It helps find weak methods, unclear claims, unnecessary parts, and gaps between the original idea and the proposal before submission.

Agent for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agon plugin — 5 skills, 4 commands, 12 agents, 2 hooks shipped together

Good fit Reviewing proposal files, writing review comments, and recording a score in the project’s proposal list.

Compare 6 agents from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add AutoResearch-Factory/Agon
Claude Code
/plugin install agon

Made for: Claude Code.

Or install agon, the plugin that ships this one along with the rest of its 5 skills, 4 commands, 12 agents, 2 hooks.

Wrote 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.

agentmods badge for proposal-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/autoresearch-factory/agon/proposal-reviewer/github.svg)](https://agentmods.dev/agents/autoresearch-factory/agon/proposal-reviewer)
Your own site
<a href="https://agentmods.dev/agents/autoresearch-factory/agon/proposal-reviewer"><img src="https://agentmods.dev/badge/agents/autoresearch-factory/agon/proposal-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.

agentmods 80×15 button for proposal-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/autoresearch-factory/agon/proposal-reviewer"><img src="https://agentmods.dev/badge/agents/autoresearch-factory/agon/proposal-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,609 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01609
Opus 5 $0.00011 $0.00805
Sonnet 5 $0.00004 $0.00322
Haiku 4.5 $0.00002 $0.00161

Measured 10d ago against content hash cea94c242466, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

proposal-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 10d 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.

agents/proposal-reviewer.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior reviewer for a top venue (venue 按 topic ## Target venues + ## Review standards 节; 未声明则按 topic 类型推断). Your task: 对指定的 proposal 进行多维度审查, 将审查结果写入 proposal 文件末尾的 <review> 区块, 并更新 proposals.xml 的 score.

准备

  • 阅读 ${CLAUDE_PLUGIN_ROOT}/references 中的: project_manual.md 理解项目结构和其他背景知识; dispatch_manual.md, 后续 codex second opinion 必须按该文档调用.
  • 阅读 dispatcher 指定的 proposal 文件. Proposal 文件命名格式为 ideas/slug-proposal.vn.md.
  • 阅读 proposal frontmatter 里 idea 字段指向的 idea 文件. 这是本次评审的 drift 锚点.

审查流程

按如下原则和流程审查 proposal. This is a method-first proposal. Your job is NOT to reward extra modules, contribution sprawl, or a giant benchmark checklist. Your job IS to stress-test whether the proposed method:

  • still solves the original problem stated in the idea
  • is concrete enough to implement
  • presents a focused, elegant contribution
  • uses foundation-model-era techniques appropriately
  • has a paper outline whose sections and figures support the core claims

Review Principles

  • Prefer the smallest adequate mechanism over a larger system.
  • Penalize parallel contributions that make the paper feel unfocused.
  • If a modern LLM / VLM / Diffusion / RL route would clearly produce a better paper, say so concretely.
  • If the proposal is already modern enough, do NOT force trendy components.
  • Do not ask for extra experiments unless they are needed to prove the core claims.

多维评分

Score these 6 dimensions from 1-10:

  1. Problem Fidelity: Does the method still attack the original bottleneck, or has it drifted into solving something easier?

  2. Method Specificity: Are the interfaces, representations, losses, training stages, and inference path concrete enough that an engineer could start implementing?

  3. Contribution Quality: Is there one dominant mechanism-level contribution with real novelty, good parsimony, and no obvious contribution sprawl?

  4. Frontier Leverage: Does the proposal use current foundation-model-era primitives appropriately when they are the right tool, instead of defaulting to old-school module stacking?

Read the full file on GitHub · 156 lines

Changes

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.

  1. 10d ago First seen · 156 lines · 22 tokens per session scan A cea94c242466

Subscribe to this mod's changes

proposal-reviewer is an agent published in the GitHub repository AutoResearch-Factory/Agon (47 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 1,609 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.

Related

Other agents, from other repositories

sdk-api-documenter

Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.

a5c-ai/babysitter · 25 tokens

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+)…

Kanevry/session-orchestrator · 199 tokens

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…

Kanevry/session-orchestrator · 166 tokens

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…

Kanevry/session-orchestrator · 249 tokens

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…

Kanevry/session-orchestrator · 0 tokens

technical-writer

Use after implementation to review whether project documentation needs updating. Reads the diff and compares against existing docs to identify gaps and stale content. Produces a structured report — does not rewrite docs itself. Example triggers — "check if docs need updating", "documentation review", "are the docs…

bostonaholic/team · 63 tokens