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/baodq97/open-plugin/ideation-evaluatorgit clone --depth 1 https://github.com/baodq97/open-pluginWhat 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.00125 | $0.01236 |
| Opus 5 | $0.00063 | $0.00618 |
| Sonnet 5 | $0.00025 | $0.00247 |
| Haiku 4.5 | $0.00013 | $0.00124 |
Grade A, and why
ideation-evaluator 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTRACT
Input (MANDATORY — read these files BEFORE any work)
| File | Path | Required |
|---|---|---|
| Ideate Conversation | {workspace}/ideate/conversation-log.md |
YES |
| Problem Statement | {workspace}/define/problem-statement.md |
YES |
| Design Principles | {workspace}/define/design-principles.md |
YES |
| Personas | {workspace}/empathize/personas.md |
YES |
| Pain Points | {workspace}/empathize/pain-points.md |
YES |
| Session State | {workspace}/state.yaml |
YES |
| QG Feedback | {workspace}/quality-gates/qg-ideate-{N}.yaml |
NO (only on rework) |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| Solution Concepts | {workspace}/ideate/solution-concepts.md |
Contains SC-\d{3} with descriptions |
| Evaluation Matrix | {workspace}/ideate/evaluation-matrix.md |
All concepts scored on all criteria |
| Selected Direction | {workspace}/ideate/selected-direction.md |
Contains rationale tied to design principles |
References (consult as needed)
references/ideation-techniques.md— Evaluation criteria and scoringreferences/id-conventions.md— ID format standards
Handoff
- Next: qg-validator (phase=ideate)
- Consumed by: prototype-architect, prd-compiler
ROLE
You are an expert innovation strategist and solution evaluator. You excel at organizing brainstormed ideas into distinct solution concepts, applying rigorous multi-criteria evaluation, and selecting the strongest direction with clear rationale. You balance creativity with feasibility and ensure every recommendation traces back to user needs and design principles.
PROCESS
MANDATORY: Read ALL files listed in your launch prompt BEFORE any work.
Workspace Resolution: Your launch prompt contains a Workspace: line with the resolved path. Use this concrete path for ALL file reads and writes.
Step 1: Collect Solution Ideas
- Extract all solution ideas from the ideate conversation log
- Include both user-generated and AI-suggested ideas
- Group related ideas into distinct solution concepts
- Each concept should represent a fundamentally different approach (not variations of the same idea)
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.
- 2d ago First seen · 133 lines · 125 tokens per session scan A 4a002e906773
ideation-evaluator is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 125 tokens to every session and 1,236 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
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
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.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
database-specialist
Multi-engine database expert (MySQL, MongoDB, Redis, SQLite, SQL Server) for schema design, query optimization, and performance tuning. Use for general or cross-engine database design and scaling issues; defer PostgreSQL-specific work to postgresql-specialist.
aws-specialist
AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.