Borrowing it
Nothing to install: this file belongs to zhouguoqing/QianYuan.AIAgenticFramework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zhouguoqing/QianYuan.AIAgenticFramework/main/.agents/skills/brainstorm/SKILL.mdgit clone --depth 1 https://github.com/zhouguoqing/QianYuan.AIAgenticFrameworkWrote 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/zhouguoqing/qianyuan.aiagenticframework/brainstorm)<a href="https://agentmods.dev/skills/zhouguoqing/qianyuan.aiagenticframework/brainstorm"><img src="https://agentmods.dev/badge/skills/zhouguoqing/qianyuan.aiagenticframework/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/zhouguoqing/qianyuan.aiagenticframework/brainstorm"><img src="https://agentmods.dev/badge/skills/zhouguoqing/qianyuan.aiagenticframework/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.00044 | $0.01161 |
| Opus 5 | $0.00022 | $0.00580 |
| Sonnet 5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
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 10d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Overview
Use this skill to convert rough ideas into clear, reviewable design outputs through structured dialogue.
The goal is to:
- Clarify requirements and constraints
- Explore alternatives with trade-offs
- Produce a concrete, validated design brief in artifacts or a handoff to planning
Workflow
Step 1: Gather Project Context
Load only the project context relevant to the current idea:
- If
docs/SUMMARY.mdexists, read it first. - Load only task-relevant detail docs.
- Prioritize
Code Standarddocs for implementation conventions. - If docs conflict with code or user intent, use the available input/question tool before broad changes.
Also check key implementation files relevant to the idea and note constraints from existing architecture, dependencies, and conventions.
Keep this pass focused. Only gather what is needed for the current idea.
Step 2: Clarify Requirements
Ask targeted questions sequentially to remove ambiguity with input/question tool:
- Focus on:
- Objective and user value
- Scope boundaries
- Constraints (technical, UX, performance, timeline)
- Success criteria
- Non-goals
Do not jump to implementation details too early.
Step 3: Explore Approaches
Propose 2-5 viable approaches.
For each approach, include:
- Short summary
- Pros
- Cons / risks
- Complexity estimate
- Recommended use conditions
Lead with your recommended option and explain why it best fits the project context and constraints.
After presenting all approaches, use input/question tool to let the user pick their preferred approach. List the summary options. Example:
- Approach A, short summary
- Approach B, short summary
- Approach C, short summary
- Other (please specify)
with the tag added for the recommended approach to guide the user.
Step 4: Present the Design Incrementally
Once requirements are clear, present the design incrementally in logical phases (about 200-300 words per phase) to avoid overwhelming the user.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 127 lines · 44 tokens per session scan A 2843c4bccefd
brainstorm is a skill published in the GitHub repository zhouguoqing/QianYuan.AIAgenticFramework (36 stars, last pushed 24d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,161 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-08-30.
Other skills, from other repositories
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
form-design
Design a form end to end — field order, grouping, validation, and completion. Use when the artifact is a form. For product-wide error strategy use error-handling-ux; for first-run signup use onboarding-design.