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 agentmods add skills/carbeneai/forge/brainstormingnpx skills add CarbeneAI/Forge --skill brainstorminggit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/brainstorming)<a href="https://agentmods.dev/skills/carbeneai/forge/brainstorming"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/brainstorming.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 | $0.00089 | $0.02826 |
| Opus 5 | $0.00044 | $0.01413 |
| Sonnet 5 | $0.00018 | $0.00565 |
| Haiku 4.5 | $0.00009 | $0.00283 |
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 4d 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming
Collaborative brainstorming that converts rough ideas into fully-formed, validated designs through structured dialogue.
🎯 Load Full CORE Context
read ${PAI_DIR}/skills/CORE/SKILL.md
When to Activate This Skill
- "brainstorm with me" → Four-phase collaborative design
- "help me think through X" → Structured exploration
- "what's the best approach for Y" → Multiple options with trade-offs
- "design a feature for Z" → Incremental design validation
- "I have an idea for..." → Idea to implementation-ready design
Core Philosophy
The Iron Law: One Question at a Time
Ask ONE question. Wait for answer. Process deeply. Ask next question.
NEVER ask multiple questions in one message. This is the foundation of effective brainstorming.
Multiple Choice Preferred
When gathering requirements, provide 2-4 options whenever possible rather than open-ended questions.
YAGNI Ruthlessly Applied
You Ain't Gonna Need It. Strip out everything not essential to the core use case. Fight scope creep at every turn.
The Four-Phase Process
Phase 1: Understanding (Questions & Requirements)
Goal: Deeply understand what the user wants to build and why.
Approach:
- Ask clarifying questions ONE AT A TIME
- Prefer multiple choice over open-ended questions
- Focus on the core use case first
- Challenge assumptions gently
- Apply YAGNI - strip out non-essential features
Example Questions:
- "What's the main problem this solves?" (not "tell me everything about your idea")
- "Who will use this? A) End users B) Developers C) Both" (not "who's the audience?")
- "Is this primarily for A) Real-time interaction B) Batch processing C) Configuration"
- "Should this handle edge case X or focus on the common path first?"
Phase Complete When: You can state the core requirement in 1-2 sentences and user confirms it's accurate.
Phase 2: Exploring Approaches
Goal: Present 2-3 viable approaches with honest trade-offs.
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.
- 4d ago First seen · 415 lines · 89 tokens per session scan A 269cc886631e
brainstorming is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 2,826 once invoked, about $0.0004 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
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…
aod-orchestrate
Multi-feature orchestration skill that bridges /aod.blueprint output to parallel wave execution. Groups synced GitHub Issues by ICE priority tier (P0/P1/P2) into sequential waves, creates Task records, spawns batch sessions via the orchestrator API, monitors completion, and reports results. Supports --issues…