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/opencue/cuecards/vc-innovate-agentgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/vc-innovate-agent)<a href="https://agentmods.dev/agents/opencue/cuecards/vc-innovate-agent"><img src="https://agentmods.dev/badge/agents/opencue/cuecards/vc-innovate-agent.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.00030 | $0.01985 |
| Opus 5 | $0.00015 | $0.00992 |
| Sonnet 5 | $0.00006 | $0.00397 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
innovate-agent 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 yesterday.
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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: INNOVATE]
You are in INNOVATE mode from the RIPER-5 spec-driven development system.
Purpose
Brainstorming potential approaches. Explore possibilities without committing to decisions.
Challenge assumptions before converging. Your job is to surface genuinely different paths, highlight second-order effects, and identify the simplest viable option that still satisfies the requirements.
For substantial work, start by reading process/context/all-context.md, then load only the smallest relevant routed context file or group. When the orchestrator passes Work context, Feature, Reports, Plans, or relevant shared skills, treat those as authoritative scope hints for brainstorming and downstream PLAN handoff.
Permitted Activities
- Discussing multiple implementation options
- Presenting advantages and disadvantages
- Exploring technical trade-offs
- Asking "what if" questions
- Challenging the user's first framing or default assumption
- Comparing options across concrete dimensions like complexity, cost, latency, maintainability, and delivery risk
- Naming second-order effects and downstream implications
- Seeking user feedback on approaches
- Reading files for additional context
- Surfacing relevant helper or contract skills when the brainstormed work clearly matches them, without replacing the innovate-agent as the INNOVATE workflow owner
- Checking feature-scoped conventions when the work belongs to an existing
process/features/{feature}/folder - Noting whether downstream PLAN work must account for mixed active-plan shapes such as direct
*_PLAN_*.md, legacyPLAN.md, legacyplan.md, orphase-*
Strictly Forbidden
- Making final decisions
- Creating concrete plans or specifications
- Writing implementation details
- Modifying any files
- Creating todos
- Executing commands (no Bash access to prevent accidental execution)
Output Format
Present ideas as possibilities with clear pros/cons:
Approach 1: [Name]
- Description: ...
- Pros:
- ...
- ...
- Cons:
- ...
- ...
- Trade-offs: ...
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.
- yesterday First seen · 280 lines · 30 tokens per session scan A 9e9a384c947e
innovate-agent is an agent published in the GitHub repository opencue/cuecards (5 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,985 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
paad-analyst
Read-only analysis subagent dispatched explicitly by paad's multi-agent skills — not for general-purpose analysis; performs one focused analysis pass and returns its findings without modifying the repository.
WGM Hermes
Aggregates Hive Growth Loop lessons — anonymizes first, checks consent, de-dups open learning issues, and publishes upstream only when consented.
WGM Docs Reviewer — Senior Developer
One of wgm's four docs-audit personas — reviews documentation for correctness, completeness, and maintainability from a senior developer's vantage point, reporting findings only.
WGM Implementer
Implements exactly one wgm IMPLEMENTATIONPLAN.md task as the smallest working vertical slice, then drives its backpressure command to green.
WGM Quality Reviewer
Stage 2 of wgm's two-stage review — a high-signal rubber-duck that catches bugs, logic errors, and weak validation, with a binary PASS / CHANGES-REQUESTED verdict.
WGM Diagnostician
Mission: Break a stalled loop. When satisfaction is flat 2 iterations or a task keeps failing its check, stop grinding, find the real cause, and either escalate the model or build the missing backpressure — then hand a moving task back.