prompt-brainstorm

prompt-brainstorm is a command for Claude Code from ihudak/ihudak-claude-plugins. It costs 51 tokens per session (1,366 once invoked), scanned A, original, MIT.

A command that records a correction to a development-workflow tool and sends it to a brainstorming process for redesign. It stores the original prompt, the problem, and the eventual resolution as plugin feedback.

In plain words
What is it for?
Use it when a development command produces the wrong result and the correction needs investigation rather than a quick retry.
Why use it?
It turns a one-off bad result into structured feedback that can be used to improve the command or workflow.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions .claude-plugin.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the workflows-core plugin — 2 skills, 6 commands, 5 agents shipped together

Good fit Use it when a development command produces the wrong result and the correction needs investigation rather than a quick retry.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ihudak/ihudak-claude-plugins
Claude Code
/plugin install workflows-core

Made for: Claude Code.

Or install workflows-core, the plugin that ships this one along with the rest of its 2 skills, 6 commands, 5 agents.

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 prompt-brainstorm

README.md
[![agentmods](https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/prompt-brainstorm/github.svg)](https://agentmods.dev/commands/ihudak/ihudak-claude-plugins/prompt-brainstorm)
Your own site
<a href="https://agentmods.dev/commands/ihudak/ihudak-claude-plugins/prompt-brainstorm"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/prompt-brainstorm/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.

agentmods 80×15 button for prompt-brainstorm

Your own site · 80×15
<a href="https://agentmods.dev/commands/ihudak/ihudak-claude-plugins/prompt-brainstorm"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/prompt-brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,366 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00051 $0.01366
Opus 5.5 $0.00020 $0.00546
Sonnet 5.5 $0.00010 $0.00273
Haiku 4.5 $0.00005 $0.00137

Measured 23d ago against content hash 8b6220a9afc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

prompt-brainstorm 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 23d 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.

plugins/workflows-core/commands/prompt-brainstorm.md · 101 lines

How it starts

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

Log a corrective interaction, then brainstorm the fix: $ARGUMENTS

/prompt-brainstorm is for when a command of this plugin family produced something wrong and the correction needs exploration rather than a one-shot fix. It captures the corrective triple as plugin feedback, then hands off to superpowers:brainstorming. origin: prompt.


Phase 0 — Specs-repo preflight

Cite ${CLAUDE_PLUGIN_ROOT}/references/specs-repo-git.md and execute its specs-preflight entry point (§3) inline: flush any leftover session artifacts from an earlier run, retry an artifact commit that failed to push, and settle the branch. This runs against $SPECS_PATH only — git -C "$SPECS_PATH", never a cd, so whatever repository you are standing in is untouched (§1 rule 1). Prompt-free and silent when the specs repo is clean and on its default branch. If a guard fires, emit its §5 notice; if it returns specs_git: blocked (§3.3 G0), carry that flag — the terminal commit-artifacts step skips on it.


Phase 1 — Identify the target

Infer the target command from recent context — which command's output you are correcting. Ask only if genuinely ambiguous (one grouped prompt of 2–4 options; the harness supplies the free-text escape). If no command applies, use n/a.

Phase 2 — Persist the corrective triple

Cite ${CLAUDE_PLUGIN_ROOT}/references/feedback-emission.md and call its emit-prompt entry point (§6). Provide:

  • Friction — what the command produced that was wrong.
  • User prompt — $ARGUMENTS, verbatim (never paraphrased).
  • Resolution — Handed off to superpowers:brainstorming to redesign the correction.
  • command (Phase 1), an inferred category (§1 vocab, reuse-first), impact, key (or null), source.

emit-prompt resolves the write target via the §2 specs-first ladder, formats the entry with the two extra prose blocks (origin: prompt), appends per §3 (never silently skipped), and writes silently. Surface the persisted path and any degradation notice.

Read the full file on GitHub · 101 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. 23d ago Changed 8b6220a9afc4
  2. 28d ago Changed 324c801ba249
  3. 1mo ago Changed · +5 lines 8eb169e549d4
  4. 1mo ago First seen · 96 lines · 51 tokens per session scan A 4df7af77816c

Subscribe to this mod's changes

prompt-brainstorm is a command published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 24d ago), licensed MIT. It adds 51 tokens to every session and 1,366 once invoked, about $0.0002 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-05.