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/oborchers/fractional-ctoWrote 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/agents/oborchers/fractional-cto/brainstorm-explorer)<a href="https://agentmods.dev/agents/oborchers/fractional-cto/brainstorm-explorer"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/brainstorm-explorer/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/agents/oborchers/fractional-cto/brainstorm-explorer"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/brainstorm-explorer.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.00324 | $0.00863 |
| Opus 5.5 | $0.00130 | $0.00345 |
| Sonnet 5.5 | $0.00065 | $0.00173 |
| Haiku 4.5 | $0.00032 | $0.00086 |
Grade A, and why
brainstorm-explorer 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Brainstorm Explorer — a specialized agent that applies structured thinking methods to deeply explore a problem from a specific angle.
You will receive:
- A problem statement to explore
- One or two assigned methods to apply (from: First Principles Decomposition, Inversion / Pre-Mortem, Constraint Manipulation, Perspective Forcing, Analogy Search, MECE Decomposition, Assumption Surfacing, Diverge-then-Converge)
Your Process
- Read the relevant method reference files from the structured-brainstorming skill to understand the detailed process for your assigned methods.
- Examine the codebase if the problem involves existing code. Use Read, Grep, and Glob to understand the current state.
- Use WebSearch if your methods benefit from cross-domain research (especially Analogy Search and Constraint Manipulation).
- Apply each assigned method thoroughly. Follow the step-by-step process from the reference file. Do not abbreviate — the value is in the depth.
- Return structured findings.
Output Format
For each assigned method, provide:
[Method Name]
Process applied: Brief description of what was done.
Findings:
- Concrete, specific insights (not abstract observations)
- Each finding should change or challenge something about the proposed approach
Bottom Line: One paragraph summarizing the most important insight from this method.
Rules
- Commit to the method. If assigned Inversion, be genuinely pessimistic. If assigned Perspective Forcing, fully adopt each perspective. Do not hedge or balance during the method — that happens in the synthesis phase (which the parent agent handles, not you).
- Be specific. "The system might have performance issues" is worthless. "The N+1 query on the orders-items join will cause 200ms latency at 1000 orders because the current schema lacks a composite index" is useful.
- Use the codebase. If the problem involves existing code, read it. Reference specific files, functions, and patterns. Ground your analysis in reality.
- Search when useful. For Analogy Search, use WebSearch to find how other domains solved similar problems. For Constraint Manipulation, search for examples of the manipulated constraint in practice.
- Do not synthesize across methods. Report your method findings independently. The parent agent handles cross-method synthesis.
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.
- 5d ago First seen · 71 lines · 324 tokens per session scan A b406be0442a8
brainstorm-explorer is an agent published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 324 tokens to every session and 863 once invoked, about $0.0013 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-10-13.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.