workflows:ideate

workflows:ideate is a skill for Claude Code, Codex from James-Traina/compound-science. It costs 26 tokens per session (680 once invoked), scanned A, original, MIT.

A research idea generator that explores many possible directions before selecting the strongest ones. It is designed for academic or data-based research questions.

In plain words
What is it for?
Use it to generate and critically filter research questions involving identification, computation, limited data, alternative estimators, relaxed assumptions, or gaps in existing work.
Why use it?
It helps avoid settling too quickly on the first plausible idea and exposes weaknesses in existing methods, data, assumptions, or evidence.

Skill for Claude CodeCodex

Part of the compound-science plugin — 20 skills shipped together

Install

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.

agentmods
npx agentmods add skills/james-traina/compound-science/workflows-ideate
Any agent
npx skills add James-Traina/compound-science --skill workflows-ideate
Clone the repo
git clone --depth 1 https://github.com/James-Traina/compound-science

Made for: Claude Code, Codex.

Or install compound-science, the plugin that ships this one along with the rest of its 20 skills.

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 workflows:ideate

README.md
[![agentmods](https://agentmods.dev/badge/skills/james-traina/compound-science/workflows-ideate.svg)](https://agentmods.dev/skills/james-traina/compound-science/workflows-ideate)
Your own site
<a href="https://agentmods.dev/skills/james-traina/compound-science/workflows-ideate"><img src="https://agentmods.dev/badge/skills/james-traina/compound-science/workflows-ideate.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 680 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00026 $0.00680
Opus 5 $0.00013 $0.00340
Sonnet 5 $0.00005 $0.00136
Haiku 4.5 $0.00003 $0.00068

Measured 3d ago against content hash af646be62d6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflows:ideate 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 3d 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.

skills/workflows-ideate/SKILL.md · 67 lines

How it starts

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

Research Ideation

Divergent exploration before convergent brainstorming. Generate many candidates, then filter ruthlessly.

Phase 0: Scope the Ideation

Read $ARGUMENTS. If the user provides a specific research question, ideate around it. If they provide a broad topic, explore broadly.

Phase 1: Generate Candidates (Divergent)

Generate 15-20 candidate research directions. Use these research-adapted ideation frames:

  1. Identification weakness — What existing results have weak identification? What new variation could fix it?
  2. Computational bottleneck — What problems are infeasible with current methods but tractable with new estimators or hardware?
  3. Data limitation workaround — What would become possible with data that is now available but underexploited?
  4. Alternative estimator class — What if the standard approach (e.g., linear IV) were replaced with a different class (e.g., ML, structural, Bayesian)?
  5. Relaxed assumption — What results depend on assumptions that could be relaxed? What happens when you relax them?
  6. Literature gap — What do practitioners need that academics haven't provided? What do adjacent fields know that this field doesn't?

Dispatch methods-explorer and literature-scout agents in parallel to ground the ideation in real methods and recent papers.

Iron rule: Generate the full candidate list before critiquing any idea. Push past the first few obvious directions.

Phase 2: Adversarial Filter (Convergent)

Entry condition: Phase 1 produced at least 15 candidate directions (the iron rule). Exit condition: 5-7 survivors identified, all rejected candidates have one-line rejection reasons.

For each candidate, evaluate:

  • Feasibility (0-100): Can this be done with available data, methods, and time?
  • Contribution (0-100): Would a top journal care about this result?
  • Identification (0-100): Is there a credible identification strategy?

Dispatch identification-critic to attack the top 10 candidates. Only candidates surviving adversarial scrutiny advance.

Read the full file on GitHub · 67 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. 3d ago First seen · 67 lines · 26 tokens per session scan A af646be62d6e

Subscribe to this mod's changes

workflows:ideate is a skill published in the GitHub repository James-Traina/compound-science (13 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 680 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 skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens