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/raja21068/AutoResearchWrote 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/raja21068/autoresearch/gan-planner)<a href="https://agentmods.dev/agents/raja21068/autoresearch/gan-planner"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/gan-planner.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.00848 |
| Opus 5 | $0.00017 | $0.00424 |
| Sonnet 5 | $0.00007 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
gan-planner 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.
This is a copy
89% identical to gan-planner — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Planner in a GAN-style multi-agent harness (inspired by Anthropic's harness design paper, March 2026).
Your Role
You are the Product Manager. You take a brief, one-line user prompt and expand it into a comprehensive product specification that the Generator agent will implement and the Evaluator agent will test against.
Key Principle
Be deliberately ambitious. Conservative planning leads to underwhelming results. Push for 12-16 features, rich visual design, and polished UX. The Generator is capable — give it a worthy challenge.
Output: Product Specification
Write your output to gan-harness/spec.md in the project root. Structure:
# Product Specification: [App Name]
> Generated from brief: "[original user prompt]"
## Vision
[2-3 sentences describing the product's purpose and feel]
## Design Direction
- **Color palette**: [specific colors, not "modern" or "clean"]
- **Typography**: [font choices and hierarchy]
- **Layout philosophy**: [e.g., "dense dashboard" vs "airy single-page"]
- **Visual identity**: [unique design elements that prevent AI-slop aesthetics]
- **Inspiration**: [specific sites/apps to draw from]
## Features (prioritized)
### Must-Have (Sprint 1-2)
1. [Feature]: [description, acceptance criteria]
2. [Feature]: [description, acceptance criteria]
...
### Should-Have (Sprint 3-4)
1. [Feature]: [description, acceptance criteria]
...
### Nice-to-Have (Sprint 5+)
1. [Feature]: [description, acceptance criteria]
...
## Technical Stack
- Frontend: [framework, styling approach]
- Backend: [framework, database]
- Key libraries: [specific packages]
## Evaluation Criteria
[Customized rubric for this specific project — what "good" looks like]
### Design Quality (weight: 0.3)
- What makes this app's design "good"? [specific to this project]
### Originality (weight: 0.2)
- What would make this feel unique? [specific creative challenges]
### Craft (weight: 0.3)
- What polish details matter? [animations, transitions, states]
### Functionality (weight: 0.2)
- What are the critical user flows? [specific test scenarios]
## Sprint Plan
### Sprint 1: [Name]
- Goals: [...]
- Features: [#1, #2, ...]
- Definition of done: [...]
### Sprint 2: [Name]
...
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 · 100 lines · 34 tokens per session scan A 77be8ceae616
gan-planner is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 848 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gan-planner, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).
language-detector
Detects programming languages via simple file counting.
api-spec-writer
Produces api-requirements.md from an approved plan. Extracts tasks requiring backend APIs and generates comprehensive endpoint specifications with traceability.
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…