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 LucasSantana-Dev/sharekit --skill brainstorminggit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/brainstorming)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/brainstorming"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/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.
<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/brainstorming"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/brainstorming.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.00041 | $0.00443 |
| Opus 5.5 | $0.00016 | $0.00177 |
| Sonnet 5.5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
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 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.
What it actually says
Brainstorming Ideas Into Designs
Help turn ideas into fully formed designs through natural collaborative dialogue.
Hard Gate
Do NOT write any code or take any implementation action until a design is presented and the user approves it.
Process
1. Explore Context
- Check current project state (files, docs, recent commits)
- Understand existing architecture
2. Ask Clarifying Questions
- One question at a time
- Prefer multiple choice when possible
- Focus on: purpose, constraints, success criteria
3. Propose Approaches
- Present 2-3 different approaches with trade-offs
- Lead with your recommendation and reasoning
4. Present Design
- Scale each section to its complexity
- Ask after each section whether it looks right
- Cover: architecture, components, data flow, error handling, testing
5. Document
- Write validated design to
docs/plans/YYYY-MM-DD-<topic>-design.md - Commit the design document
6. Transition to Implementation
- Create an implementation plan (use
planskill)
Key Principles
- One question at a time — Don't overwhelm
- YAGNI ruthlessly — Remove unnecessary features
- Explore alternatives — Always propose 2-3 approaches
- Incremental validation — Present design, get approval
- Be flexible — Go back and clarify when needed
Outputs / Evidence
- Return the concrete deliverable requested, the main decisions made, and any unresolved constraints.
Failure / Stop Conditions
- Stop if key prerequisites are missing or the request changes scope enough that the current workflow no longer fits.
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 · 67 lines · 41 tokens per session scan A d5c82c4eb4e0
brainstorming is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 443 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
get-context
Mandatory design-brief gate for clarifying the product and outcome. Use before ideation, image-to-code builds, redesigns, or product UI work to clarify missing product information and play back the brief before proceeding.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
cli-anything-photoshop
A command-line tool that controls Adobe Photoshop through Windows automation. It can work with Photoshop documents, layers, selections, text, image adjustments, and exports.
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.