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 skills/omerakben/code-oz/brainstormingnpx skills add omerakben/code-oz --skill brainstorminggit clone --depth 1 https://github.com/omerakben/code-ozWhat 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.00029 | $0.01526 |
| Opus 5 | $0.00015 | $0.00763 |
| Sonnet 5 | $0.00006 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
brainstorming 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advisory only — not an enforced gate. For enforced gates and a different-model review, run
code-oz run.
Where this skill sits
This is advice, and it is the lowest-priority voice in the room. Your user's
instructions, the project's CLAUDE.md, the code-oz engine contracts, and any
system or developer constraints all outrank this skill. When any of them
conflict with anything below, follow them and ignore this skill. This skill
never overrides those instructions, and nothing here changes your existing
operating rules — it only offers a way to think before you build.
Brainstorming a feature before you build
Use this when someone says "help me think through this feature design" or wants to explore requirements and trade-offs before any code lands. The goal is a clearer shared picture, not a decision you stamp.
How to run the conversation
- Restate the problem in one or two sentences, in your own words, and check it back. If you cannot restate it, you do not understand it yet — ask.
- Name who the feature is for and the one concrete moment they hit the problem. A feature with no named consumer is a guess.
- List the constraints that are already fixed: existing contracts, the data you have, the time budget, the parts of the codebase you must not touch.
- Sketch two or three approaches, not one. For each, write the cost, the risk, and what it rules out later.
- Surface the open questions explicitly. Write down what you do not know and what evidence would close each gap.
- Pick a direction only when the user does. Record the assumption it rests on.
What good output looks like
- A short problem statement the user agrees with.
- A named consumer and the moment of use.
- Two or more approaches with honest trade-offs.
- A list of open questions, each with the evidence that would resolve it.
This is exploration. It does not approve a design, satisfy a phase gate, or stand in for the engine's DEFINE phase. It helps you arrive at the conversation the engine's gates then enforce.
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 · 127 lines · 29 tokens per session scan A cdf0b9ed24c7
brainstorming is a skill published in the GitHub repository omerakben/code-oz (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,526 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-31.
Other skills, from other repositories
skill-creator
Scaffold, author, and validate an Agent Skill. Use when the user wants to create a new skill, turn a repeatable workflow into a reusable SKILL.md, or fix a skill that fails to load.
E2E Testing Nori Skillsets Subcommands
Use when you need to interactively test a nori-skillsets CLI subcommand end-to-end via tmux, with full filesystem isolation.
TUI Puppeteering with tmux
Use when automating or testing TUI/CLI applications - provides isolated tmux sessions with scripts for input, output capture, and state verification.
issue-review
Triage a copperhead GitHub issue, attempt reproduction, and check it against the spec. Use when the user asks to review an issue, e.g. /issue-review 42 or /issue-review .
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…
visualize
Create visualizations and interactive tools directly in conversation. Use when asked to show how something works, make simulators or labs, maps, plots, charts or graphs, comparisons, UI mockups, scenarios, adjustable inputs, and exploration beyond regular text.