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/architecture-scenario-explorer)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/architecture-scenario-explorer"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/architecture-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/architecture-scenario-explorer"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/architecture-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.00017 | $0.02793 |
| Opus 5 | $0.00009 | $0.01396 |
| Sonnet 5 | $0.00003 | $0.00559 |
| Haiku 4.5 | $0.00002 | $0.00279 |
Grade A, and why
architecture-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 4d 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Scenario Explorer
Explore architectural decisions through systematic scenario analysis with trade-off evaluation and future-proofing assessment.
Instructions
You are tasked with systematically exploring architectural decisions through comprehensive scenario modeling to optimize system design choices. Follow this approach: $ARGUMENTS
1. Prerequisites Assessment
Critical Architecture Context Validation:
- System Scope: What system or component architecture are you designing?
- Scale Requirements: What are the expected usage patterns and growth projections?
- Constraints: What technical, business, or resource constraints apply?
- Timeline: What is the implementation timeline and evolution roadmap?
- Success Criteria: How will you measure architectural success?
If context is unclear, guide systematically:
Missing System Scope:
"What specific system architecture needs exploration?
- New System Design: Greenfield application or service architecture
- System Migration: Moving from legacy to modern architecture
- Scaling Architecture: Expanding existing system capabilities
- Integration Architecture: Connecting multiple systems and services
- Platform Architecture: Building foundational infrastructure
Please specify the system boundaries, key components, and primary functions."
Missing Scale Requirements:
"What are the expected system scale and usage patterns?
- User Scale: Number of concurrent and total users
- Data Scale: Volume, velocity, and variety of data processed
- Transaction Scale: Requests per second, peak load patterns
- Geographic Scale: Single region, multi-region, or global distribution
- Growth Projections: Expected scaling timeline and magnitude"
2. Architecture Option Generation
Systematically identify architectural approaches:
Architecture Pattern Matrix
Architectural Approach Framework:
Monolithic Patterns:
- Layered Architecture: Traditional n-tier with clear separation
- Modular Monolith: Well-bounded modules within single deployment
- Plugin Architecture: Core system with extensible plugin ecosystem
- Service-Oriented Monolith: Internal service boundaries with single deployment
Distributed Patterns:
- Microservices: Independent services with business capability alignment
- Service Mesh: Microservices with infrastructure-level communication
- Event-Driven: Asynchronous communication with event sourcing
- CQRS/Event Sourcing: Command-query separation with event storage
Hybrid Patterns:
- Modular Microservices: Services grouped by business domain
- Micro-Frontend: Frontend decomposition matching backend services
- Strangler Fig: Gradual migration from monolith to distributed
- API Gateway: Centralized entry point with backend service routing
Cloud-Native Patterns:
- Serverless: Function-based with cloud provider infrastructure
- Container-Native: Kubernetes-first with cloud-native services
- Multi-Cloud: Cloud-agnostic with portable infrastructure
- Edge-First: Distributed computing with edge location optimization
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.
- 4d ago First seen · 382 lines · 17 tokens per session scan A 9bc369fe44aa
architecture-scenario-explorer is a command published in the GitHub repository davepoon/buildwithclaude (3,429 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 2,793 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.