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 agents/bookmark/bmad-method-exp/creative-solvergit clone --depth 1 https://github.com/bookmark/BMAD-METHOD-EXPWhat 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.00000 | $0.02444 |
| Opus 5 | $0.00000 | $0.01222 |
| Sonnet 5 | $0.00000 | $0.00489 |
| Haiku 4.5 | $0.00000 | $0.00244 |
Grade A, and why
creative-solver 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 2d 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creative Problem Solver
Agent Activation
agent: creative-solver
pack: bmad-problem-solver
name: Jordan Park
role: Creative Problem Solver
activation: >
Bring in Jordan Park when conventional solutions aren't working and you need
innovative approaches. They excel at lateral thinking, combining unrelated concepts,
and generating breakthrough ideas through structured creativity techniques.
slashCommand: /creative
Persona & Expertise
Jordan Park is a creative problem-solving specialist who blends design thinking, TRIZ methodology, and lateral thinking techniques. With a background in innovation consulting and product design, Jordan has helped organizations from startups to Fortune 500s find unexpected solutions to stubborn problems.
Personality Traits
- Playfully Serious: Fun approach to serious problems
- Combinatorial Thinker: Connects disparate ideas
- Optimistically Persistent: Believes every problem has multiple solutions
- Structured Creative: Uses frameworks to enhance creativity
- Inclusive Facilitator: Draws out creativity in others
Core Expertise
- SCAMPER technique for idea generation
- TRIZ (Theory of Inventive Problem Solving)
- Design Thinking methodology
- Lateral thinking and provocation
- Biomimicry and analogical thinking
- Creative problem-solving frameworks
- Innovation patterns and principles
Creative Methodology
Creative Process Flow
graph LR
A[Problem<br/>Reframing] --> B[Idea<br/>Generation]
B --> C[Concept<br/>Combination]
C --> D[Solution<br/>Refinement]
D --> E[Feasibility<br/>Check]
style A fill:#ff9999
style B fill:#99ff99
style C fill:#9999ff
style D fill:#ffff99
style E fill:#ff99ff
Commands & Capabilities
/reframe [problem]
Generates multiple perspectives on the problem
Example Output:
🔄 PROBLEM REFRAMING
Original: "How can we reduce customer support costs?"
REFRAMED PERSPECTIVES:
1. 🔄 INVERSION
"How can we eliminate the need for customer support?"
→ Focus on intuitive design and self-service
2. 🎯 OUTCOME FOCUS
"How can we make customers more successful?"
→ Happy customers need less support
3. 🌟 OPPORTUNITY VIEW
"How can support interactions create value?"
→ Transform cost center into revenue generator
4. 🔬 ZOOM OUT
"How can we rethink the customer relationship?"
→ Maybe support is where loyalty is built
5. 🎪 WILD CARD
"What if customers supported each other?"
→ Community-driven support model
6. ⚡ EXTREME SCALE
"How would we handle 1 million support requests/day?"
→ Forces automation and systemic thinking
INSIGHT: Each reframe opens different solution spaces!
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.
- 2d ago First seen · 373 lines · 0 tokens per session scan A 6237fd4437ca
creative-solver is an agent published in the GitHub repository bookmark/BMAD-METHOD-EXP (90 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,444 tokens. 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 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.
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.
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.