davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/business-scenario-explorer)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/business-scenario-explorer"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/business-scenario-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/commands/davepoon/buildwithclaude/business-scenario-explorer"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/business-scenario-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.00012 | $0.02075 |
| Opus 5 | $0.00006 | $0.01038 |
| Sonnet 5 | $0.00002 | $0.00415 |
| Haiku 4.5 | $0.00001 | $0.00208 |
Grade A, and why
business-scenario-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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Scenario Explorer
Explore multiple business timeline scenarios with constraint validation and decision optimization.
Instructions
You are tasked with creating a comprehensive business scenario simulation to help explore multiple future timelines and make better strategic decisions. Follow this systematic approach: $ARGUMENTS
1. Prerequisites Assessment
Before proceeding, validate these critical inputs:
- Business Context: Is the core business model and industry clearly defined?
- Time Horizon: What is the planning timeline (quarters, years, market cycles)?
- Key Variables: What are the primary factors that could change outcomes?
- Success Metrics: How will you measure scenario success/failure?
- Decision Points: What specific decisions need to be made?
If any of these are unclear, use progressive questioning:
Missing Business Context:
"I need to understand your business model better. Please describe:
- Your primary revenue streams
- Key cost drivers
- Main competitive advantages
- Target market segments"
Missing Time Horizon:
"What planning period should we simulate?
- Short-term (3-6 months): Market response, product launches
- Medium-term (1-2 years): Strategic initiatives, market expansion
- Long-term (3-5+ years): Industry transformation, market cycles"
Missing Key Variables:
"What factors could significantly impact your business?
- Market conditions (growth, recession, disruption)
- Competitive landscape changes
- Regulatory shifts
- Technology adoption
- Customer behavior evolution"
2. Constraint Modeling
Map the decision environment with systematic constraint analysis:
External Constraints
- Market size and growth dynamics
- Competitive positioning and responses
- Regulatory environment and compliance requirements
- Economic conditions and cycles
- Technology adoption curves
- Supply chain dependencies
Internal Constraints
- Financial resources and burn rate
- Team capabilities and capacity
- Technology infrastructure limitations
- Brand positioning and reputation
- Customer base characteristics
- Operational scalability factors
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 · 335 lines · 12 tokens per session scan A bae9d4a15ea3
business-scenario-explorer is a command published in the GitHub repository davepoon/buildwithclaude (3,434 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 2,075 once invoked, about $0.0001 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-09-05.
Other commands, from other repositories
convert-to-todowrite-tasklist-prompt
Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.
security-audit
Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
test-basic-role-override
Test Type: Fundamental prompt injection detection Risk Level: High Expected Detection: Role manipulation attempts.
audit
Perform security audit on codebase.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.