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 skills add alexmond/alexmskills --skill brainstorm-panelgit clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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.
[](https://agentmods.dev/skills/alexmond/alexmskills/brainstorm-panel)<a href="https://agentmods.dev/skills/alexmond/alexmskills/brainstorm-panel"><img src="https://agentmods.dev/badge/skills/alexmond/alexmskills/brainstorm-panel/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.
<a href="https://agentmods.dev/skills/alexmond/alexmskills/brainstorm-panel"><img src="https://agentmods.dev/badge/skills/alexmond/alexmskills/brainstorm-panel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 34 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00125 | $0.04907 |
| Opus 5 | $0.00063 | $0.02454 |
| Sonnet 5 | $0.00025 | $0.00981 |
| Haiku 4.5 | $0.00013 | $0.00491 |
Grade A, and why
brainstorm-panel 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 9d 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm Panel
Try it:
/brainstorm-panel:brainstorm-panel make this landing page headline more convincing— or say "brainstorm a better onboarding flow".
You hand this skill a piece of work; it decides who should be in the room and how they should work together, then runs them. The premise is that the best panel and the best process are functions of the task, not fixed in advance — a landing page needs a different room and a different rhythm than a contract clause or an algorithm. So the skill's first job is diagnosis, and only then does it convene.
The flow
- Read the work and the project context, and diagnose what it needs.
- Compose a team — propose the roles and why each earns a seat.
- Pick a management style — propose how the panel will be coordinated and why.
- Present the roster for review — the user adds, removes, or swaps members — then run the brainstorming loop once they approve.
- Deliver the result plus the reasoning trail.
- Capture what worked — per-role wisdom to the panel's roles registry, the run record to the panel log — so the next target starts smarter.
Steps 2 and 3 are the skill's value: don't ask the user to pick the roster or the process — propose them, with rationale, from the work and the repo. Step 6 is what makes the panel improve at this repo over time rather than starting cold each run.
Step 1 — Diagnose the work
Read what the user gave you and characterize it before convening anyone:
- Type: open ideation, improving an existing artifact, choosing between options, or stress-testing a plan? (This drives the management style.)
- Quality axes: which dimensions actually matter here — correctness, appeal, persuasion, performance, clarity, credibility, cost? (This drives the roster.)
- Artifact: is there a concrete thing to edit (a file, a draft, a design), or is this greenfield? If there's a file, note its exact path; only it is in scope.
- Goal & bar: what does "good" look like, in the user's terms? If the user didn't say, infer a working bar and state it — they can correct it.
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.
- 9d ago First seen · 372 lines · 125 tokens per session scan A eb4719079bc3
brainstorm-panel is a skill published in the GitHub repository alexmond/alexmskills (6 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 4,907 once invoked, about $0.0006 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
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
blind-spot-pass
Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.