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 agentmods add skills/phuonghx/aim-cli/brainstormingnpx skills add phuonghx/aim-cli --skill brainstorminggit clone --depth 1 https://github.com/phuonghx/aim-cliWhat 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 | $0.00086 | $0.01523 |
| Opus 5 | $0.00043 | $0.00762 |
| Sonnet 5 | $0.00017 | $0.00305 |
| Haiku 4.5 | $0.00009 | $0.00152 |
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 yesterday.
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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Build Questioning & Communication
Treat this as a checkpoint you must pass through before writing code for anything complex, underspecified, or new.
Two responsibilities live here:
- Ask first. Surface the decisions that shape an implementation before committing to one.
- Stay legible. Report progress, failures, and outcomes in a way the user can act on.
🛑 The Questioning Gate
What flips the gate on
| Incoming request | Required move |
|---|---|
| "Build / create / make X" with thin detail | 🛑 Pose ~3 questions first |
| A sizeable feature or architectural choice | 🛑 Pin down direction before coding |
| "Change / update / tweak X" | 🛑 Lock the scope before touching it |
| Fuzzy or open-ended ask | 🛑 Probe purpose, audience, limits |
Step 0 — Consult memory first
Before generating any questions, look for accumulated context so you don't re-ask what's already settled:
CHECK: Is .aim-agents/memory/MEMORY.md present?
├─ Found → Read its index, quietly reuse relevant prior decisions,
│ and drop any question the memory already answers.
└─ Absent → Run the full gate below as normal.
The gate, step by step
- HALT — resist the urge to start coding.
- RECALL — scan
.aim-agents/memory/for anything already decided on this topic. - PROBE — raise at least three questions (omitting ones memory has covered):
- 🎯 Purpose — which problem does this solve?
- 👥 Audience — who actually uses it?
- 📦 Scope — what's essential versus optional?
- PAUSE — wait for the reply before moving on.
- PERSIST — once the direction is clear, record the calls made with
/remember [decision].
This gate is the backbone of the /brainstorm workflow.
🧠 Building Questions on the Fly
⛔ Canned question lists are off-limits. Every question is generated from the actual request. The full method lives in dynamic-questioning.md; the essentials:
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.
- yesterday First seen · 180 lines · 86 tokens per session scan A 56bed98fce5a
brainstorming is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 1,523 once invoked, about $0.0004 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-31.
Other skills, from other repositories
hs-release
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
hindsight-local
Store user preferences, learnings from tasks, and procedure outcomes. Use to remember what works and recall context before new tasks. (user).
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).
user-persona
Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use empathy-map; for motivation framing use jobs-to-be-done.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).