ideate

A timed brainstorming workflow that pairs one agent proposing an idea with another reviewing it from a user’s perspective. It repeats this process until the set time ends.

In plain words
What is it for?
Use it to brainstorm features, approaches, or solutions for a defined topic and duration.
Why use it?
It helps generate several options while exposing weak or impractical ideas. The time limit keeps the exploration focused.

Skill for Claude CodeCodex

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/av/harbor/ideate
Any agent
npx skills add av/harbor --skill ideate
Clone the repo
git clone --depth 1 https://github.com/av/harbor

Made for: Claude Code, Codex.

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,635 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.00089 $0.02635
Opus 5 $0.00044 $0.01318
Sonnet 5 $0.00018 $0.00527
Haiku 4.5 $0.00009 $0.00264

Measured yesterday against content hash 432c26d1791a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

.agents/skills/ideate/SKILL.md · 266 lines

How it starts

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

Ideate

Generate, stress-test, and rank ideas on any topic through iterative propose-and-critique cycles. Each iteration dispatches two subagents: one to propose an idea, one to tear it apart from the end-user perspective. The clock controls when you stop. The critique scores control what survives.

Your Role

You are the orchestrator. You do three things:

  1. Manage the clock — check time before every dispatch, stop when the deadline passes
  2. Dispatch subagent pairs — a proposer and a critic, every iteration
  3. Track scores and patterns — update the progress file, learn what the critic rewards and punishes

You do NOT propose ideas yourself. You do NOT critique ideas yourself. You do NOT do any research, code reading, or analysis. All intellectual work happens inside subagents. Your context is reserved for the dispatch loop and pattern tracking.

The Iron Law

YOU DO NOT DECIDE WHEN IDEATION IS DONE. THE CLOCK DECIDES.

Keep dispatching propose-and-critique pairs until the deadline passes. You have zero authority to judge "enough ideas" or "good enough." The user gave you a duration. You use all of it.

Inputs

The user provides two things:

  1. Topic — what to ideate on (e.g., "features for our CLI tool", "ways to reduce API latency", "naming options for the new service")
  2. Duration — how long to ideate (e.g., "30 minutes", "1 hour", "2 hours")

If the duration is vague ("a while"), interpret as 1 hour. If truly ambiguous, ask once.

Optionally, the user may specify:

  • Top N — how many ideas to present at the end (default: 3)
  • Context — a codebase, document, or domain to ground proposals in

The Process

digraph ideate {
    rankdir=TB;
    node [shape=box];

    start [label="Record start time\nCompute deadline" shape=doublecircle];
    init [label="Create progress file\nin /tmp"];
    check [label="Check current time\nagainst deadline" shape=diamond];
    read_log [label="Read progress file\nfor patterns"];
    propose [label="Dispatch PROPOSER\nsubagent"];
    critique [label="Dispatch CRITIC\nsubagent"];
    update [label="Update progress file\nwith score + patterns"];
    present [label="Present top N ideas\nwith scores + critiques" shape=doublecircle];

    start -> init -> check;
    check -> read_log [label="time remains"];
    check -> present [label="deadline passed"];
    read_log -> propose;
    propose -> critique;
    critique -> update;
    update -> check;
}

Read the full file on GitHub · 266 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 266 lines · 89 tokens per session scan A 432c26d1791a

Subscribe to this mod's changes

ideate is a skill published in the GitHub repository av/harbor (3,198 stars, last pushed 2d ago), licensed Apache-2.0. It adds 89 tokens to every session and 2,635 once invoked, about $0.0004 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

docker-local-build

Build and test Kurtosis from source on local Docker. Compiles all components (engine, core, files-artifacts-expander), builds Docker images, installs the CLI, and restarts the engine. Use when developing Kurtosis and testing changes locally with Docker.

kurtosis-tech/kurtosis · 56 tokens

files-inspect

Inspect, download, upload, and debug Kurtosis file artifacts. View artifacts in an enclave, download them locally for inspection, upload local files, and troubleshoot file mounting issues. Use when services can't find expected files or configs are wrong.

kurtosis-tech/kurtosis · 51 tokens

k8s-dev-deploy

Build, push, and deploy Kurtosis dev images to a Kubernetes cluster without creating a release. Rebuilds engine, core, and files-artifacts-expander as multi-arch Docker images with a unique tag, pushes to the logged-in user's Docker Hub, and restarts the engine. Use when testing local code changes on a k8s cluster.

kurtosis-tech/kurtosis · 78 tokens

starlark-dev

Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.

kurtosis-tech/kurtosis · 50 tokens

docker-debug

Debug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.

kurtosis-tech/kurtosis · 45 tokens

enclave-inspect

Inspect and manage Kurtosis enclaves. List enclaves, view services and ports, examine file artifacts, dump enclave state for debugging, and clean up. Use when you need to understand what's running inside an enclave or export its state.

kurtosis-tech/kurtosis · 52 tokens