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/clean-branches)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/clean-branches"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/clean-branches/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/clean-branches"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/clean-branches.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.00007 | $0.01792 |
| Opus 5.5 | $0.00003 | $0.00717 |
| Sonnet 5.5 | $0.00001 | $0.00358 |
| Haiku 4.5 | $0.00001 | $0.00179 |
Grade A, and why
clean-branches 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Branches Command
Clean up merged and stale git branches
Instructions
Follow this systematic approach to clean up git branches: $ARGUMENTS
-
Repository State Analysis
- Check current branch and uncommitted changes
- List all local and remote branches
- Identify the main/master branch name
- Review recent branch activity and merge history
# Check current status git status git branch -a git remote -v # Check main branch name git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@' -
Safety Precautions
- Ensure working directory is clean
- Switch to main/master branch
- Pull latest changes from remote
- Create backup of current branch state if needed
# Ensure clean state git stash push -m "Backup before branch cleanup" git checkout main # or master git pull origin main -
Identify Merged Branches
- List branches that have been merged into main
- Exclude protected branches (main, master, develop)
- Check both local and remote merged branches
- Verify merge status to avoid accidental deletion
# List merged local branches git branch --merged main | grep -v "main\\|master\\|develop\\|\\*" # List merged remote branches git branch -r --merged main | grep -v "main\\|master\\|develop\\|HEAD" -
Identify Stale Branches
- Find branches with no recent activity
- Check last commit date for each branch
- Identify branches older than specified timeframe (e.g., 30 days)
- Consider branch naming patterns for feature/hotfix branches
# List branches by last commit date git for-each-ref --format='%(committerdate) %(authorname) %(refname)' --sort=committerdate refs/heads # Find branches older than 30 days git for-each-ref --format='%(refname:short) %(committerdate)' refs/heads | awk '$2 < "'$(date -d '30 days ago' '+%Y-%m-%d')'"' -
Interactive Branch Review
- Review each branch before deletion
- Check if branch has unmerged changes
- Verify branch purpose and status
- Ask for confirmation before deletion
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 · 250 lines · 7 tokens per session scan A c4601ba5e030
clean-branches is a command published in the GitHub repository davepoon/buildwithclaude (3,660 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 1,792 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
create-release-note
Generate comprehensive release documentation from recent commits, producing two distinct outputs: a customer-facing release note and a technical engineering note.
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…
setup
Verify ClauDex prerequisites — Codex CLI, authentication, and git.
release
Execute full version release — merge PRs, version bump, tag, GitHub Release, sync branches, cleanup.
pre-pr
Run complete validation workflow before creating PR.
pr
A pull-request or merge-request description generator based on the changes in Git and, when available, a software specification.