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.
git clone --depth 1 https://github.com/Workflowsio/company-os-starter-kitWrote 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/commands/workflowsio/company-os-starter-kit/brainstorm)<a href="https://agentmods.dev/commands/workflowsio/company-os-starter-kit/brainstorm"><img src="https://agentmods.dev/badge/commands/workflowsio/company-os-starter-kit/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/commands/workflowsio/company-os-starter-kit/brainstorm"><img src="https://agentmods.dev/badge/commands/workflowsio/company-os-starter-kit/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.00018 | $0.01403 |
| Opus 5.5 | $0.00007 | $0.00561 |
| Sonnet 5.5 | $0.00004 | $0.00281 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
workflows: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 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm a GTM Strategy or Business Approach
Note: The current year is 2026. Use this when dating brainstorm documents.
This command loads the brainstorming and document-review skills, which this kit does not ship. If a skill is not installed, follow this file's own inline instructions for that step and say in the run summary that you did.
Brainstorming helps answer WHAT to pursue through collaborative dialogue. It precedes /workflows:plan, which answers HOW to execute it.
Process knowledge: Load the brainstorming skill for detailed question techniques, approach exploration patterns, and prioritization principles.
Topic Description
<topic_description> #$ARGUMENTS </topic_description>
If the topic description above is empty, ask the user: "What would you like to explore? Describe the campaign angle, market opportunity, positioning challenge, or growth idea you're thinking about."
Do not proceed until you have a topic description from the user.
Execution Flow
Phase 0: Assess Requirements Clarity
Evaluate whether brainstorming is needed based on the topic description.
Clear requirements indicators:
- Specific target audience and value prop defined
- Referenced existing playbook or proven pattern
- Described exact desired outcome with metrics
- Constrained, well-defined scope
If requirements are already clear:
Use AskUserQuestion tool to suggest: "Your brief seems detailed enough to proceed directly to planning. Should I run /workflows:plan instead, or would you like to explore the idea further?"
Phase 1: Understand the Opportunity
1.1 Context Research (Lightweight)
Run a quick scan to understand existing context:
- Task repo-research-analyst("Understand existing context related to: <topic_description>")
Focus on: similar campaigns run before, established playbooks, client history, CLAUDE.md guidance.
1.2 Collaborative Dialogue
Use the AskUserQuestion tool to ask questions one at a time.
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 · 164 lines · 18 tokens per session scan A bb22bea23f00
workflows:brainstorm is a command published in the GitHub repository Workflowsio/company-os-starter-kit (104 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,403 once invoked, about $0.0001 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-11-09.
workflows:brainstorm compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| workflows:brainstormWorkflowsio/company-os-starter-kit | Command | 104 | yesterday | MIT | A | 18 | Claude Code |
| _registry-protocolChappygo-OS/Atomic-Spec | Command | 10 | 4d ago | MIT | A | 0 | Claude Code |
| mach12:gh-pr-readLeanAndMean/scramjet | Command | 8 | 8d ago | Apache-2.0 | A | 25 | Claude Code |
| scramjet:troubleshootLeanAndMean/scramjet | Command | 8 | 8d ago | Apache-2.0 | A | 9 | Claude Code |
| gaai-auditdigipulse-engineering/GAAI-framework | Command | 163 | 8d ago | none | A | 10 | Claude Code |
| cold-startkunalsuri/ai-fication-kit | Command | 3 | 26d ago | Apache-2.0 | A | 28 | GitHub Copilot |
| healthalexgreensh/token-optimizer | Command | 2.9k | yesterday | none | C | 28 | Claude Code |