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.
npx agentmods add commands/davepoon/buildwithclaude/check-filegit 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/check-file)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/check-file"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/check-file.svg" alt="Measured on agentmods" 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.00021 | $0.00362 |
| Opus 5 | $0.00010 | $0.00181 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
check-file 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 yesterday.
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.
What it actually says
File Analysis Tool
Perform comprehensive analysis of $ARGUMENTS to identify code quality issues, security vulnerabilities, and optimization opportunities.
Task
I'll analyze the specified file and provide detailed insights on:
- Code quality metrics and maintainability
- Security vulnerabilities and best practices
- Performance bottlenecks and optimization opportunities
- Dependency usage and potential issues
- TypeScript/JavaScript specific patterns and improvements
- Test coverage and missing tests
Process
I'll follow these steps:
- Read and parse the target file
- Analyze code structure and complexity
- Check for security vulnerabilities and anti-patterns
- Evaluate performance implications
- Review dependency usage and imports
- Provide actionable recommendations for improvement
Analysis Areas
Code Quality
- Cyclomatic complexity and maintainability metrics
- Code duplication and refactoring opportunities
- Naming conventions and code organization
- TypeScript type safety and best practices
Security Assessment
- Input validation and sanitization
- Authentication and authorization patterns
- Sensitive data exposure risks
- Common vulnerability patterns (XSS, injection, etc.)
Performance Review
- Bundle size impact and optimization opportunities
- Runtime performance bottlenecks
- Memory usage patterns
- Lazy loading and code splitting opportunities
Best Practices
- Framework-specific patterns (React, Vue, Angular)
- Modern JavaScript/TypeScript features usage
- Error handling and logging practices
- Testing patterns and coverage gaps
I'll provide specific, actionable recommendations tailored to your project's technology stack and architecture.
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.
- yesterday First seen · 60 lines · 21 tokens per session scan A f200d4146426
check-file is a command published in the GitHub repository davepoon/buildwithclaude (3,419 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 362 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.
organize-files
Organize and rename files based on content analysis.