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/add-package)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/add-package"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/add-package/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/add-package"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/add-package.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.00006 | $0.00758 |
| Opus 5.5 | $0.00002 | $0.00303 |
| Sonnet 5.5 | $0.00001 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
add-package 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Package to Workspace
Add and configure new project dependencies
Instructions
-
Package Definition and Analysis
- Parse package name and type from arguments:
$ARGUMENTS(format: name [type]) - If no arguments provided, prompt for package name and type
- Validate package name follows workspace naming conventions
- Determine package type: library, application, tool, shared, service, component-library
- Check for naming conflicts with existing packages
- Parse package name and type from arguments:
-
Package Structure Creation
- Create package directory in appropriate workspace location (packages/, apps/, libs/)
- Set up standard package directory structure based on type:
src/for source codetests/or__tests__/for testingdocs/for package documentationexamples/for usage examples (if library)public/for static assets (if application)
- Create package-specific configuration files
-
Package Configuration Setup
- Generate package.json with proper metadata:
- Name following workspace conventions
- Version aligned with workspace strategy
- Dependencies and devDependencies
- Scripts for build, test, lint, dev
- Entry points and exports configuration
- Configure TypeScript (tsconfig.json) extending workspace settings
- Set up package-specific linting and formatting rules
- Generate package.json with proper metadata:
-
Package Type-Specific Setup
- Library: Configure build system, export definitions, API documentation
- Application: Set up routing, environment configuration, build optimization
- Tool: Configure CLI setup, binary exports, command definitions
- Shared: Set up common utilities, type definitions, shared constants
- Service: Configure server setup, API routes, database connections
- Component Library: Set up Storybook, component exports, styling system
-
Workspace Integration
- Register package in workspace configuration (nx.json, lerna.json, etc.)
- Configure package dependencies and peer dependencies
- Set up cross-package imports and references
- Configure workspace-wide build order and dependencies
- Add package to workspace scripts and task runners
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.
- 1mo ago First seen · 89 lines · 6 tokens per session scan A d642568315c0
add-package is a command published in the GitHub repository davepoon/buildwithclaude (3,660 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 758 once invoked, about $0.0000 per session on Opus 5.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
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable, then Phase 6 post-merge close once the PR is verified merged. Not Done until…
auto-dev
A command that autonomously develops each pending requirement in a shared product blueprint using a requirements-first software-development process.
add-to-todos
Add todo item to TO-DOS.md with context from conversation.
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
create-plan
Create hierarchical project plans for solo agentic development (briefs, roadmaps, phase plans).
mainframe-tickets-implement
This is a user-invocable command. Execute it only because the current invocation explicitly selected it. It takes no arguments: every invocation processes the complete current project queue that is ready for implementation.