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 AcKeskin/contexture --skill brainstormgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/ackeskin/contexture/brainstorm)<a href="https://agentmods.dev/skills/ackeskin/contexture/brainstorm"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/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/ackeskin/contexture/brainstorm"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/brainstorm.svg" alt="Reviewed on agentmods" width="80" 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.00115 | $0.01210 |
| Opus 5.5 | $0.00046 | $0.00484 |
| Sonnet 5.5 | $0.00023 | $0.00242 |
| Haiku 4.5 | $0.00012 | $0.00121 |
Grade A, and why
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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brainstorm
The ideation organ. The stage before /envision: where a half-formed or blurry idea gets talked into enough shape that /envision can take it. One organ, two moods — discuss (explore a loose idea) and crystallize (pin a blurry one down) — they're the same conversation at different stages, so there's one verb.
[half-formed idea] → /brainstorm → shaped idea (.claude/ideas/<slug>.md) → /envision → /spec → …
The discipline: it must converge, not just chat. A /brainstorm that ends without a crystallized statement the user accepts was just conversation. The engineer wants the idea sharpened, not a transcript.
When to run
/brainstorm [slug]— start (or resume) shaping an idea.- Natural language: "help me shape this idea", "I have a vague idea for X", "let's think this through", "crystallize this", "put a name and edges on this".
- Do not auto-fire. Mode A. Not for an idea that's already shaped (go straight to
/envisionor/spec), not for a one-line task (just do it).
Procedure
1. Resolve slug + read any prior note
- Slug given → use it. Omitted → derive a short kebab slug from the idea once it has a name, or ask.
- If
.claude/ideas/<slug>.mdexists, read it and resume from where it left off (this is the cross-session-gap recovery the persisted note buys).
2. Discuss — explore, but steer toward shape
Talk the idea through. Free-form, but every few turns pull toward the five things a shaped idea needs (below). Surface tensions, ask the question that's load-bearing, offer framings — but do not drift into spec-level detail (functions, files, schemas): that's /spec's job downstream. When the user starts there, redirect: "that's implementation — let's pin what this is first."
The five things to converge on:
- Name — what to call it.
- Description — one paragraph: what it is, who it's for, the one-sentence success criterion.
- Edges — what's in and, more importantly, what's explicitly out (the non-goals that keep it from absorbing scope).
- End goal — what "done / working" looks like.
- Open edges — the questions still genuinely unresolved (carried forward, not forced).
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.
- 1mo ago First seen · 84 lines · 115 tokens per session scan A a3cd060ee65e
brainstorm is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 1,210 once invoked, about $0.0005 per session on Opus 5.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
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
agent-go-expert
Specialist subagent: Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
agent-svelte-expert
Specialist subagent: Svelte 5 runes, SvelteKit routing, form actions, and compile-time reactivity specialist. Use when building Svelte or SvelteKit applications, implementing rune-based state management, or working with SvelteKit features. Trigger phrases: Svelte, SvelteKit, runes, $state, $derived, $effect, $props…
literature-review-planner
Structured literature review planning with systematic methodology, source evaluation, and synthesis frameworks. Use when planning academic literature reviews, research surveys, systematic reviews, or scoping reviews.