skill-check: Skill for Claude Code

.agents/skills/brainstorming/SKILL.md

brainstorming is a skill for Claude Code, Codex from thedaviddias/skill-check. It costs 32 tokens per session (1,016 once invoked), scanned A, a copy of brainstorming, MIT.

A planning conversation for turning a software idea into an agreed design before implementation. It explores the project, asks clarifying questions, compares approaches, and records the design.

In plain words
What is it for?
It helps plan features, components, configuration changes, and behavior changes, then save the approved plan in the project documentation.
Why use it?
It helps expose unclear requirements and risky assumptions before code is written.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is thedaviddias/skill-check's own configuration. It tells Claude Code and Codex how to work on skill-check itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything skill-check configures →

Reuse

Borrowing it

Nothing to install: this file belongs to thedaviddias/skill-check. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/thedaviddias/skill-check/main/.agents/skills/brainstorming/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/thedaviddias/skill-check

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for brainstorming

README.md
[![agentmods](https://agentmods.dev/badge/skills/thedaviddias/skill-check/brainstorming/github.svg)](https://agentmods.dev/skills/thedaviddias/skill-check/brainstorming)
Your own site
<a href="https://agentmods.dev/skills/thedaviddias/skill-check/brainstorming"><img src="https://agentmods.dev/badge/skills/thedaviddias/skill-check/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.

agentmods 80×15 button for brainstorming

Your own site · 80×15
<a href="https://agentmods.dev/skills/thedaviddias/skill-check/brainstorming"><img src="https://agentmods.dev/badge/skills/thedaviddias/skill-check/brainstorming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,016 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01016
Opus 5 $0.00016 $0.00508
Sonnet 5 $0.00006 $0.00203
Haiku 4.5 $0.00003 $0.00102

Measured 9d ago against content hash 4a629bc1bbba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 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.

Origin

This is a copy

94% identical to brainstorming — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/brainstorming/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Brainstorming Ideas Into Designs

Overview

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.

Anti-Pattern: "This Is Too Simple To Need A Design"

Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.

Checklist

You MUST create a task for each of these items and complete them in order:

  1. Explore project context — check files, docs, recent commits
  2. Ask clarifying questions — one at a time, understand purpose/constraints/success criteria
  3. Propose 2-3 approaches — with trade-offs and your recommendation
  4. Present design — in sections scaled to their complexity, get user approval after each section
  5. Write design doc — save to docs/plans/YYYY-MM-DD-<topic>-design.md and commit
  6. Transition to implementation — invoke writing-plans skill to create implementation plan

Process Flow

digraph brainstorming {
    "Explore project context" [shape=box];
    "Ask clarifying questions" [shape=box];
    "Propose 2-3 approaches" [shape=box];
    "Present design sections" [shape=box];
    "User approves design?" [shape=diamond];
    "Write design doc" [shape=box];
    "Invoke writing-plans skill" [shape=doublecircle];

    "Explore project context" -> "Ask clarifying questions";
    "Ask clarifying questions" -> "Propose 2-3 approaches";
    "Propose 2-3 approaches" -> "Present design sections";
    "Present design sections" -> "User approves design?";
    "User approves design?" -> "Present design sections" [label="no, revise"];
    "User approves design?" -> "Write design doc" [label="yes"];
    "Write design doc" -> "Invoke writing-plans skill";
}

Read the full file on GitHub · 97 lines

Changes

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.

  1. 9d ago First seen · 97 lines · 32 tokens per session scan A 4a629bc1bbba

Subscribe to this mod's changes

brainstorming is a skill published in the GitHub repository thedaviddias/skill-check (188 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,016 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to brainstorming, differing in 2 lines, and is treated as a copy.