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/agent-preflightgit 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/agent-preflight)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/agent-preflight"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/agent-preflight.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.00009 | $0.00600 |
| Opus 5 | $0.00005 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
agent-preflight 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 today.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Preflight
Run this before letting Claude Code, Codex, Cursor, or another coding agent modify a real repository. The goal is to make the agent produce a short, reviewable safety receipt before any file-changing work starts.
Instructions
-
Identify the proposed agent task
- Restate the requested change in one sentence.
- List the files, directories, commands, secrets, services, and package managers the agent is likely to touch.
- Flag any task that asks for credentials, payment details, KYC, production deploys, destructive commands, private prompt extraction, or unclear external network access.
-
Map the repository blast radius
- Inspect the project layout, dependency manifests, test commands, CI config, lockfiles, and deployment files.
- Identify protected paths such as
.env*, secrets, auth code, billing code, migration files, infra config, release scripts, and generated artifacts. - Separate safe read-only exploration from write operations.
-
Score the change before editing
- Mark the task
Greenwhen it is local, reversible, tested, and limited to low-risk files. - Mark it
Yellowwhen it touches dependencies, config, generated code, authentication-adjacent logic, or unclear test coverage. - Mark it
Redwhen it may expose secrets, change payment/auth/deployment behavior, delete data, or run untrusted code.
- Mark the task
-
Create guardrails for the agent run
- State the allowed files and commands.
- State the blocked files and commands.
- Require a branch or patch workflow for Yellow/Red work.
- Require tests, lint, or a dry-run command before reporting success.
- Require the agent to stop and ask before crossing any listed boundary.
-
Produce a preflight receipt
- Output a concise Markdown receipt with: task summary, risk level, allowed scope, blocked scope, test plan, rollback plan, and exact stop conditions.
- Do not perform the actual implementation in the same response unless the user explicitly approves the receipt.
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.
- today First seen · 65 lines · 9 tokens per session scan A 0049c2b58380
agent-preflight is a command published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 600 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
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.
off
Turn claude-bionify off so Claude's replies render normally.