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/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/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/opencue/cuecards/vc-innovate-agent"><img src="https://agentmods.dev/badge/agents/opencue/cuecards/vc-innovate-agent.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.00030 | $0.01985 |
| Opus 5.5 | $0.00012 | $0.00794 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago First seen · 280 lines · 30 tokens per session scan A 9e9a384c947e
innovate-agent is an agent published in the GitHub repository opencue/cuecards (6 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,985 once invoked, about $0.0001 per session on Opus 5.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
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
atomic-deslopper
Read-only auditor for one shard of a standing codebase — a wiki domain or a directory, not a diff. Sweeps the files it is given for accumulated slop: comment noise, AI-tell doc prose, speculative abstraction, hand-rolled stdlib, duplicate helpers, dead code, errors used as control flow, and drift from the repo's own…
atomic-strategist
Heavyweight reasoning agent. Runs at high effort on the caller's model. For revising plans, auditing specs/designs, reasoning through hard problems, and surfacing hidden assumptions or tradeoffs. Read-only. Does not implement, does not gate diffs, does not locate code. Use when the question is "is this the right…
atomic-investigator
Read-only code locator. Answers "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Returns file:line table, no prose. Refuses to suggest fixes or speculate about design. Use to save main-context tokens on exploration.
atomic-wiki-writer
Writes one wiki page from source. Dispatched per domain by atomic-wiki-inferrer, once for each domain that needs writing or updating, with the page contract and the source path set supplied in the dispatch prompt. Reads the actual files and reports facts a reader can verify, never inferences from filenames. Carries…