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-review)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/architecture-review"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/architecture-review/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-review"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/architecture-review.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.00005 | $0.00710 |
| Opus 5 | $0.00003 | $0.00355 |
| Sonnet 5 | $0.00001 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
architecture-review 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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Review Command
Review and improve system architecture
Instructions
Perform a comprehensive architectural analysis following these steps:
-
High-Level Architecture Analysis
- Map out the overall system architecture and components
- Identify architectural patterns in use (MVC, MVP, Clean Architecture, etc.)
- Review module boundaries and separation of concerns
- Analyze the application's layered structure
-
Design Patterns Assessment
- Identify design patterns used throughout the codebase
- Check for proper implementation of common patterns
- Look for anti-patterns and code smells
- Assess pattern consistency across the application
-
Dependency Management
- Review dependency injection and inversion of control
- Analyze coupling between modules and components
- Check for circular dependencies
- Assess dependency direction and adherence to dependency rule
-
Data Flow Architecture
- Trace data flow through the application
- Review state management patterns and implementation
- Analyze data persistence and storage strategies
- Check for proper data validation and transformation
-
Component Architecture
- Review component design and responsibilities
- Check for single responsibility principle adherence
- Analyze component composition and reusability
- Assess interface design and abstraction levels
-
Error Handling Architecture
- Review error handling strategy and consistency
- Check for proper error propagation and recovery
- Analyze logging and monitoring integration
- Assess resilience and fault tolerance patterns
-
Scalability Assessment
- Analyze horizontal and vertical scaling capabilities
- Review caching strategies and implementation
- Check for stateless design where appropriate
- Assess performance bottlenecks and scaling limitations
-
Security Architecture
- Review security boundaries and trust zones
- Check authentication and authorization architecture
- Analyze data protection and privacy measures
- Assess security pattern implementation
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.
- 3d ago First seen · 104 lines · 5 tokens per session scan A 4d5caf68857a
architecture-review is a command published in the GitHub repository davepoon/buildwithclaude (3,429 stars, last pushed today), licensed MIT. It adds 5 tokens to every session and 710 once invoked, about $0.0000 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
check-best-practices
Analyze code against language-specific best practices, coding standards, and community conventions to improve code quality and maintainability.
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
refactor-code
Command "refactor-code" from centminmod/my-claude-code-setup, covering refactoring analysis command, your task, refactoring analysis framework, core principles (for analysis) and multi-agent analysis workflow.
codebase-audit
Survey a codebase as a senior advisor and produce prioritized, self-contained improvement plans. Read-only on source code. Use standalone before iteration-start to discover what's worth doing, or independently to build a prioritized backlog.
review
Review branch changes against Archcore docs, or report project health; --drift runs staleness detection, --deep a full documentation audit.
review-code
A command that reviews selected code changes as a strict defect gate before merging. It also supports a separate audit mode.