Borrowing it
Nothing to install: this file belongs to getappz/agentflare. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/getappz/agentflare/master/.claude/skills/brainstorming/SKILL.mdgit clone --depth 1 https://github.com/getappz/agentflareWrote 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/getappz/agentflare/brainstorming)<a href="https://agentmods.dev/skills/getappz/agentflare/brainstorming"><img src="https://agentmods.dev/badge/skills/getappz/agentflare/brainstorming/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/getappz/agentflare/brainstorming"><img src="https://agentmods.dev/badge/skills/getappz/agentflare/brainstorming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00087 | $0.01469 |
| Opus 5.5 | $0.00035 | $0.00588 |
| Sonnet 5.5 | $0.00017 | $0.00294 |
| Haiku 4.5 | $0.00009 | $0.00147 |
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 2mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming
Classify a request before touching it, then gate implementation on that
classification. requirements-specification turns an already-concrete ask
into testable requirements; this skill runs before that — while the ask
is still "build me X" or "can we..." and scope isn't pinned down yet.
The gate
The gate is one-way: if a task turns out bigger than its classification mid-work, stop and reclassify upward. Never reclassify downward to skip a step you've already started.
Classify first
State the classification out loud before asking anything else — "this reads as Bounded, so I'll sketch the design in chat rather than write a spec" — so the user can correct it immediately.
- Spike — a feasibility question ("can we...", "is X possible...", "quick and dirty is fine"). The output is an answer, not code to keep. State the question and the 2-3 sentence probe plan, get a nod, then investigate as cheaply as correctness allows. No design doc. Report back as a recommendation; label anything you built as throwaway.
- Bounded — a well-scoped change to a flow that already exists in this repo: a new flag, a small endpoint, a one-file fix. "I understand this kind of app" is not enough — bounded means the code you'd change is already there to read. Ask the clarifying questions that matter, present a short design in chat (a few sentences to a short paragraph: approach, files touched, how you'll verify it), then stop for approval. No spec file.
- Architectural — a new subsystem, a new project, or a change that
restructures how components fit together or alters an interface other
code depends on. Ask clarifying questions, propose 2-3 approaches with
trade-offs and a recommendation, then stop for approval. Once approved,
hand off to
system-architecture-designfor the structural decision and/orrequirements-specificationfor the spec — no implementation plan exists until that handoff's output is itself approved.
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.
- 2mo ago First seen · 124 lines · 87 tokens per session scan A de9cadd35767
brainstorming is a skill published in the GitHub repository getappz/agentflare (2 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 1,469 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
audit
Fast quality gate — detects stack, runs static analysis, checks cross-layer consistency, fixes issues. Run between every pipeline phase, before every commit push, after every feature batch. Lighter than /analyze but catches the same critical issues.
logic-lens
AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…