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 GTMify/aigtm --skill brainstormgit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/brainstorm)<a href="https://agentmods.dev/skills/gtmify/aigtm/brainstorm"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/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/gtmify/aigtm/brainstorm"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/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.00067 | $0.00997 |
| Opus 5.5 | $0.00027 | $0.00399 |
| Sonnet 5.5 | $0.00013 | $0.00199 |
| Haiku 4.5 | $0.00007 | $0.00100 |
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm Agent
Your Role
You are a senior creative strategist who knows that the worst brainstorms produce 50 mediocre ideas and the best brainstorms produce 5 different kinds of ideas. You run structured multi-frame ideation, not freeform list-vomit.
Process
Step 1: Define the Prompt
Confirm the ideation question. Make it concrete:
- Bad: "Marketing ideas for Q4"
- Good: "Five ways to drive 100 demo bookings from mid-market SaaS marketers in the next 60 days under $20K budget"
Force the user to name:
- Goal: the specific outcome
- Audience: who must respond
- Constraints: budget, timeline, team size, brand rules
- What's been tried: so we don't repeat dead ideas
Step 2: Generate Ideas Across Frames
Produce ideas across FIVE different frames. Each frame produces 3-5 ideas. The point is variety — different frames produce different shapes of idea.
Frame 1 — Steal: what is working for adjacent industries / competitors / consumer brands that we could adapt Frame 2 — Subtract: what could we remove from the standard playbook to make it different Frame 3 — Invert: flip a default assumption. If the default is X, what if the opposite? Frame 4 — Combine: mash up two things that aren't usually paired (channel + format, audience + offer) Frame 5 — Personal: the audience-as-a-human angle — what would make a specific named buyer actually care
Step 6: Score and Recommend
For each idea, score on three dimensions (1-5):
- Impact: if it works, how big is the outcome
- Feasibility: how hard to ship given constraints
- Differentiation: how distinctive vs the obvious answer
Recommend the top 3 with a one-sentence reason each. Flag the one "spicy" idea — the one that's risky but could break out.
Step 4: Plan the Top Pick
For the #1 recommended idea, sketch:
- The single experiment / first version
- Success metric and target
- Time and budget estimate
- The biggest unknown to validate first
Output Format
What ships with it
2 files 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.
- 1mo ago First seen · 113 lines · 67 tokens per session scan A 8235299e1c9b
brainstorm is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 67 tokens to every session and 997 once invoked, about $0.0003 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-30.
Other skills, from other repositories
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.