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 TheBeardedBearSAS/claude-craft --skill socratic-brainstormgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/socratic-brainstorm)<a href="https://agentmods.dev/skills/thebeardedbearsas/claude-craft/socratic-brainstorm"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/socratic-brainstorm/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/thebeardedbearsas/claude-craft/socratic-brainstorm"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/socratic-brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01244 |
| Opus 5 | $0.00023 | $0.00622 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
socratic-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 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.
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.
Socratic Brainstorm — Clarifier avant de coder
Skill inspiré de obra/superpowers. Objectif : forcer une phase de questions ciblées avant toute implémentation, pour éviter de coder la mauvaise chose très vite.
Règle d'or : une question coûte 30 secondes, un faux développement coûte 3 jours.
Méthode socratique : 5 familles de questions
À poser avant de toucher au code. Pas toutes à chaque fois — choisir les plus pertinentes selon le contexte.
1. Questions sur le PROBLÈME
- Quel est le vrai problème à résoudre ? (pas la solution supposée)
- Pour qui ? Quel persona / rôle utilisateur ?
- Quel est le coût de ne rien faire ?
- Comment mesurera-t-on le succès ? (KPI, métrique)
- Y a-t-il une solution plus simple qui résout 80% du besoin ?
2. Questions sur les CONTRAINTES
- Contraintes métier : règles légales, compliance, SLA ?
- Contraintes techniques : stack imposée, dépendances, legacy ?
- Contraintes temporelles : deadline, dépendances externes ?
- Contraintes ressources : budget infra, RH, maintenance long terme ?
- Que ne faut-il surtout pas casser ?
3. Questions sur les ALTERNATIVES
- Quelles sont les 3 approches possibles ? (minimum)
- Pourquoi celle-ci plutôt qu'une autre ?
- Qu'a-t-on déjà essayé / envisagé ?
- Existe-t-il une solution off-the-shelf (lib, SaaS) ?
- Peut-on ne rien coder (config, manuel, process) ?
4. Questions sur les HYPOTHÈSES
- Qu'est-ce qu'on suppose sans avoir vérifié ?
- Quel est le volume / trafic attendu ?
- Quel est le pattern d'usage réel (95% cas / 5% edge cases) ?
- Quels acteurs externes impliqués ? (API tierces, équipes, utilisateurs)
- Que se passe-t-il si cette hypothèse est fausse ?
5. Questions sur les CONSÉQUENCES
- Qu'est-ce qui change pour l'utilisateur final ?
- Impact sur les autres features / modules ?
- Coûts d'exploitation (infra, monitoring, support) ?
- Comment rollback si ça tourne mal ?
- Comment évolue cette solution dans 1 an, 3 ans ?
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 · 124 lines · 47 tokens per session scan A 9f01770dfad4
socratic-brainstorm is a skill published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,244 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
embedded-iot
Embedded systems firmware, microcontrollers (ESP32, STM32, Arduino, Raspberry Pi), RTOS (FreeRTOS, Zephyr), IoT protocols (MQTT, CoAP, BLE), bare-metal C/C++, and hardware peripheral interfaces (I2C, SPI, UART, GPIO). Use when developing firmware, working with microcontrollers, or building IoT devices.
finding-files
Use when searching for files by name, pattern, or type in large directories, or building file lists for pipelines with other tools.
querying-json
Use when querying JSON files, filtering or transforming JSON data, or extracting specific fields from large JSON files without loading entire file contents (saves 80-95% context).
red-synthesize-green
Use when implementing any feature or fix using TDD, before writing any implementation code.