Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Bounce ideas off Codex. An agent skill from SnakeO/claude-co-commands.
Install Co Brainstorm
$ npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SnakeO/claude-co-commands co-brainstorm --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SnakeO/claude-co-commands.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/co-commands/skills/co-brainstorm .claude/skills/co-brainstorm && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "co-brainstorm" agent skill from https://github.com/SnakeO/claude-co-commands/tree/master/plugins/co-commands/skills/co-brainstorm into .claude/skills/co-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "co-brainstorm", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SnakeO/claude-co-commands/tree/master/plugins/co-commands/skills/co-brainstormType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SnakeO/claude-co-commands co-brainstorm --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SnakeO/claude-co-commands.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/co-commands/skills/co-brainstorm .agents/skills/co-brainstorm && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "co-brainstorm" agent skill from https://github.com/SnakeO/claude-co-commands/tree/master/plugins/co-commands/skills/co-brainstorm into .agents/skills/co-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "co-brainstorm", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SnakeO/claude-co-commands co-brainstorm --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SnakeO/claude-co-commands.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/co-commands/skills/co-brainstorm .cursor/skills/co-brainstorm && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "co-brainstorm" agent skill from https://github.com/SnakeO/claude-co-commands/tree/master/plugins/co-commands/skills/co-brainstorm into .cursor/skills/co-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "co-brainstorm", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SnakeO/claude-co-commands.git --path plugins/co-commands/skills/co-brainstorm--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SnakeO/claude-co-commands co-brainstorm --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SnakeO/claude-co-commands.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/co-commands/skills/co-brainstorm .gemini/skills/co-brainstorm && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "co-brainstorm" agent skill from https://github.com/SnakeO/claude-co-commands/tree/master/plugins/co-commands/skills/co-brainstorm into .gemini/skills/co-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "co-brainstorm", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SnakeO/claude-co-commands co-brainstormInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SnakeO/claude-co-commands.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/co-commands/skills/co-brainstorm .github/skills/co-brainstorm && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "co-brainstorm" agent skill from https://github.com/SnakeO/claude-co-commands/tree/master/plugins/co-commands/skills/co-brainstorm into .github/skills/co-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "co-brainstorm", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SnakeO/claude-co-commands co-brainstorm --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SnakeO/claude-co-commands.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/co-commands/skills/co-brainstorm .opencode/skills/co-brainstorm && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "co-brainstorm" agent skill from https://github.com/SnakeO/claude-co-commands/tree/master/plugins/co-commands/skills/co-brainstorm into .opencode/skills/co-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "co-brainstorm", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
co-brainstorm- GitHub stars
- 148
- Token cost
- ~1.3k tokens
- SKILL.md length
- 583 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Bounce ideas off Codex. An agent skill from SnakeO/claude-co-commands.
- Works in 3 steps: Start Codex and Hand It to a Background… → Do Your Own Brainstorming → Retrieve and Compare
- You want fast alternative ideas
- SKILL.md covers How Codex Is Reached, Step 1: Start Codex and Hand…, Step 2: Do Your Own… and Step 3: Retrieve and Compare, plus 2 more sections
- Calls go, claude and codex
What it does
Co Brainstorm is an agent skill from SnakeO/claude-co-commands. Bounce ideas off Codex. Use when you want fast alternative ideas, critiques, and perspectives on any topic. Triggers an interactive conversation with Codex for brainstorming and exploration.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Brainstorming. It works with Bash. The repository describes itself as: Co- planning, validation, and brainstorming commands for Claude Code via Codex MCP. The licence is MIT.
When your agent uses it
- You want fast alternative ideas
- Perspectives on any topic
- An interactive conversation with Codex for brainstorming and exploration
Example prompts
- “/co-brainstorm”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7c477b2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
goclaudecodex
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Co Brainstorm loads about 1.3k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 583 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SnakeO/claude-co-commands at commit 7c477b2, republished under its MIT licence (© SnakeO). 583 words, ~1,257 tokens.
Download SKILL.mdSave it as
.claude/skills/co-brainstorm/SKILL.md (or your agent's skills folder).- name
- co-brainstorm
- description
- Bounce ideas off Codex. Use when you want fast alternative ideas, critiques, and perspectives on any topic. Triggers an interactive conversation with Codex for brainstorming and exploration.
Co-Brainstorm: Bounce Ideas Off Codex
How Codex Is Reached
Codex runs through its CLI, driven by the helper script scripts/codex-session, which lives two
levels above this skill's base directory: call it as <base directory>/../../scripts/codex-session.
It keeps one Codex conversation per session folder and always runs Codex in its read-only sandbox:
codex-session new <label>makes a session folder and prints its pathcodex-session run <DIR>sends<DIR>/prompt.mdas the first message and waits for the replycodex-session read <DIR>prints Codex's latest replycodex-session reply <DIR>sends a follow-up read from stdin and prints the reply
Shell variables do not survive between Bash calls, so always use the literal folder path.
Step 1: Start Codex and Hand It to a Background Subagent
Create the session and write Codex's first message, in one Bash call:
bash DIR="$(<base directory>/../../scripts/codex-session new co-brainstorm)" && echo "$DIR" cat > "$DIR/prompt.md" <<'CODEX_PROMPT' Brainstorm on the following topic. Think deeply, explore multiple angles, and prepare your ideas, reading the code in the working directory where it helps — but do NOT share them yet. If you need to ask clarifying questions about the topic before brainstorming, ask them now. Otherwise, when your brainstorming is complete and you have fully formed ideas ready, respond with exactly: "My brainstorming is complete and I'm ready to present" and nothing else. Wait for my next message before sharing your ideas. Topic: $ARGUMENTS CODEX_PROMPTSpawn a background subagent (Agent tool with
run_in_background: true) to handle all communication with Codex. Give it the helper path and the folder path, and tell it to:- Run
<helper> run <DIR>in the foreground, with the Bash tool's longest timeout (600000 ms). It can take several minutes. - Run
<helper> read <DIR>. If Codex replied "My brainstorming is complete and I'm ready to present", go to step 4. - If Codex asked clarifying questions instead, answer them using its own judgment and the
code in the working directory, by sending a follow-up (quote the heredoc delimiter):
<helper> reply <DIR> <<'CODEX_PROMPT'…CODEX_PROMPT. Then check the reply again as in step 2. If Codex sent its full ideas instead of the ready message, treat it as ready. - Report back only that Codex is ready, the session folder, and how many questions it answered. Do NOT request or repeat Codex's ideas; that happens in Step 3.
The subagent handles the back-and-forth so you are free to do your own work. In a non-interactive session (
claude -p), do these steps yourself in the foreground instead: background work is killed when that kind of session ends.- Run
Show full SKILL.md (254 more words)Show less
Step 2: Do Your Own Brainstorming
While the subagent communicates with Codex in the background, do your own independent brainstorming on the topic. Think through:
- Multiple approaches and alternatives
- Trade-offs and risks
- Edge cases and constraints
- Creative or unconventional angles
Write down your own ideas and perspectives. Do NOT check the Codex result until you have finished your own brainstorming. The entire point is to produce two independent sets of ideas and then compare them — reading Codex's ideas early defeats this purpose and introduces bias.
Step 3: Retrieve and Compare
Only after your brainstorming is complete, confirm the background subagent has reported that Codex is ready. Then ask Codex for its ideas in the same conversation; the command prints it:
<base directory>/../../scripts/codex-session reply <DIR> <<'CODEX_PROMPT'
Go ahead, share your ideas.
CODEX_PROMPTIf the subagent reported that Codex did not reply, show the user the error it relayed (it names
the fix, such as codex login) and continue with your own brainstorming alone.
Once the ideas arrive:
- Read the Codex brainstorm output.
- Compare it against your own ideas and look for:
- Perspectives you missed
- Simpler or more creative alternatives
- Risks or edge cases you overlooked
- Integrate useful ideas into your thinking and discard the rest.
Continuing the Conversation
To dig deeper, send a follow-up in the same Codex conversation. It prints Codex's answer:
<base directory>/../../scripts/codex-session reply <DIR> <<'CODEX_PROMPT'
your follow-up: challenge assumptions, explore alternatives, test edge cases
CODEX_PROMPTHow to Treat Responses
Treat Codex responses as coming from a junior developer:
- Never assume suggestions are correct; validate each one yourself.
- You are the lead engineer and have final say.
- Use responses as a starting point, not authoritative answers.
© SnakeO, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/co-commands/skills/co-brainstorm of SnakeO/claude-co-commands.
Open the folder on GitHubat commit 7c477b2
Compare with similar skills
Co Brainstorm next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Co Brainstorm this skillSnakeO/claude-co-commands | 148 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Plugin Settings Patternanthropics/claude-plugins-official | 38k | 7 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 54 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
- Official
Plugin Settings Pattern
anthropics/claude-plugins-official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Kimi Code Delegation
CherryHQ/cherry-studio
Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.
More from SnakeO/claude-co-commands
Co Plan
SnakeO/claude-co-commands
Generate a parallel plan via Codex. An agent skill from SnakeO/claude-co-commands.
Co Validate
SnakeO/claude-co-commands
Get a staff engineer review of your plan via Codex. An agent skill from SnakeO/claude-co-commands.
Related
Works with
Categories
Questions about Co Brainstorm
What does Co Brainstorm do?
Bounce ideas off Codex. An agent skill from SnakeO/claude-co-commands. Co Brainstorm is an agent skill from SnakeO/claude-co-commands. Bounce ideas off Codex.
When should I use Co Brainstorm?
Co Brainstorm fits situations like: you want fast alternative ideas; perspectives on any topic; an interactive conversation with Codex for brainstorming and exploration.
How do I install Co Brainstorm in Claude Code?
Run `npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a claude-code`. Or copy the skill folder (plugins/co-commands/skills/co-brainstorm in SnakeO/claude-co-commands) into .claude/skills/co-brainstorm in your project. Claude Code loads it when a task matches its description.
How do I install Co Brainstorm in Codex?
Run `npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a codex`. Or copy the skill folder (plugins/co-commands/skills/co-brainstorm in SnakeO/claude-co-commands) into .agents/skills/co-brainstorm in your project. Codex loads it when a task matches its description.
Can I use Co Brainstorm in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SnakeO/claude-co-commands --skill co-brainstorm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/co-brainstorm, .gemini/skills/co-brainstorm, .github/skills/co-brainstorm and .opencode/skills/co-brainstorm in your project.
What does Co Brainstorm need to run?
Going by SKILL.md and its folder, Co Brainstorm needs the command-line tools its instructions call (go, claude and codex).
Does Co Brainstorm access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Co Brainstorm safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Co Brainstorm use?
Co Brainstorm is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Co Brainstorm use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Co Brainstorm?
Skills that share tags, products or a category with Co Brainstorm: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars), Brainstorming (xpinjection/test-driven-spring-boot, 112 stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Co Brainstorm?
SnakeO (a GitHub user) maintains it in SnakeO/claude-co-commands, which has 148 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 28, 2026.
Source: SnakeO/claude-co-commands on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.