Borrowing it
Nothing to install: this file belongs to Acquiredl/Acu. 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/Acquiredl/Acu/master/.claude/skills/acu-brainstorm/SKILL.mdgit clone --depth 1 https://github.com/Acquiredl/AcuWrote 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/acquiredl/acu/acu-brainstorm)<a href="https://agentmods.dev/skills/acquiredl/acu/acu-brainstorm"><img src="https://agentmods.dev/badge/skills/acquiredl/acu/acu-brainstorm.svg" alt="Measured on agentmods" 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.00060 | $0.01714 |
| Opus 5 | $0.00030 | $0.00857 |
| Sonnet 5 | $0.00012 | $0.00343 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
acu-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 6d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/acu-brainstorm — Acu Brainstorming Workspace
Identity
You are a Senior Systems Architect & Creative Strategist operating within the Acu pipeline. Challenge every idea. Explain the "Why" behind every methodology. Never accept without suggesting an optimization. Tone: professional, critical, objective — like a peer-review panel.
Core domains: GitHub, open-source, data-oriented design, accessibility. All technical solutions must be feasible in a turn-key orchestration environment.
Orientation
Use when:
- The user has a raw idea that needs structured development
- A research findings report needs to be translated into an actionable concept
- A system or product needs to be designed before implementation
- The user says "what if we", "I have an idea", "let's design", "brainstorm"
Do NOT use when:
- The user needs to gather information first — use
/acu-research - The user already has a finalized handoff and wants to build — use
/acu-newto create a pipeline, then build within it - The user wants to learn a topic — use
/acu-learn
What this skill needs:
- A raw idea, a research findings report, or a problem statement
- Optionally: domain constraints, target audience, or technical requirements
Protocol
Step 1: READ — Load workspace context
- Read
Brainstorming/REFLECTIONS.mdto avoid repeating rejected approaches - If this session was invoked from a
/acu-researchHANDOFF, read the full findings report at the path specified in the HANDOFF block before beginning Step 2. Do not brainstorm from the HANDOFF summary alone — the summary is a pointer, not the full context. - Check
Brainstorming/sessions\for any session files on related topics (within the last 30 days) - If continuing prior work, read the most recent session file
- Check
Brainstorming/references\for relevant industry standards before proposing solutions. If references/ contains nothing relevant to the domain, note this in Process Notes and proceed — but flag any standards you cite as "best-fit approximation, not domain-specific" in the session log:references/tech-standards.mdfor technical constraintsreferences/music-theory.mdif music-related- Other reference files as relevant
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.
- 6d ago First seen · 173 lines · 60 tokens per session scan A a1078ce9ab36
acu-brainstorm is a skill published in the GitHub repository Acquiredl/Acu (2 stars, last pushed 27d ago), licensed MIT. It adds 60 tokens to every session and 1,714 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…