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 PedroMosquera/squadai --skill brainstorminggit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/brainstorming)<a href="https://agentmods.dev/skills/pedromosquera/squadai/brainstorming"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/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.1 | $0.00013 | $0.00401 |
| Opus 5 | $0.00006 | $0.00200 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
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 8d 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.
What it actually says
Brainstorming Skill
Explore requirements and generate comprehensive test scenarios before any code is written. This skill is the first phase of the TDD pipeline.
Steps
-
Understand the problem: Ask clarifying questions before generating scenarios.
- What is the expected input and output?
- What are the success criteria?
- Are there performance or security constraints?
- Who are the consumers of this functionality?
-
Identify happy paths: List the primary usage flows.
- Core feature usage with typical inputs
- Most common call patterns
- Expected return values and side effects
-
Identify edge cases: Enumerate boundary and exceptional conditions.
- Empty inputs, nil/null values, zero values
- Maximum/minimum boundary values
- Concurrent access scenarios (if applicable)
- Large inputs or long-running operations
-
Identify error scenarios: List all failure modes.
- Invalid input (wrong type, out-of-range, malformed)
- Missing dependencies (unavailable service, missing file)
- Permission or authentication failures
- Partial failures (some items succeed, some fail)
-
Prioritize scenarios: Rank by risk and importance.
- Critical: covers behavior that breaks the system if wrong
- Important: covers common usage patterns
- Nice-to-have: covers unusual but valid edge cases
Output Format
Produce a numbered list of test scenarios grouped by category:
Happy Paths
- [Scenario: input → expected output]
Edge Cases
- [Scenario: edge condition → expected behavior]
Error Scenarios
- [Scenario: error condition → expected error or fallback]
Do NOT write code. Only produce the scenario list. The Planner converts this into a test plan; the Implementer writes the code.
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.
- 8d ago First seen · 57 lines · 13 tokens per session scan A 5cf34fa45320
brainstorming is a skill published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 401 once invoked, about $0.0001 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
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
ijfw-tdd
RED-GREEN-REFACTOR enforcement. Use when implementing a feature or bugfix before writing implementation code. Trigger: tdd, test first, red green refactor, /ijfw-tdd.
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…