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-to-changelog)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/add-to-changelog"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/add-to-changelog/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-to-changelog"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/add-to-changelog.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.00017 | $0.00419 |
| Opus 5 | $0.00009 | $0.00210 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
add-to-changelog 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 7d 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.
What it actually says
Update Changelog
Add a new entry to the project's CHANGELOG.md file based on the provided arguments.
Parse Arguments
Parse $ARGUMENTS to extract:
- Version number (e.g., "1.1.0")
- Change type: "added", "changed", "deprecated", "removed", "fixed", or "security"
<message>is the description of the change
Examples
/add-to-changelog 1.1.0 added "New markdown to BlockDoc conversion feature"
/add-to-changelog 1.0.2 fixed "Bug in HTML renderer causing incorrect output"
Description
This command will:
- Check if a CHANGELOG.md file exists and create one if needed
- Look for an existing section for the specified version
- If found, add the new entry under the appropriate change type section
- If not found, create a new version section with today's date
- Format the entry according to Keep a Changelog conventions
- Commit the changes if requested
The CHANGELOG follows the Keep a Changelog format and Semantic Versioning.
Implementation
The command should:
- Parse the arguments to extract version, change type, and message
- Read the existing CHANGELOG.md file if it exists
- If the file doesn't exist, create a new one with standard header
- Check if the version section already exists
- Add the new entry in the appropriate section
- Write the updated content back to the file
- Suggest committing the changes
Remember to update the package version in __init__.py and setup.py if this is a new version.
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.
- 7d ago First seen · 54 lines · 17 tokens per session scan A 830f20b64751
add-to-changelog is a command published in the GitHub repository davepoon/buildwithclaude (3,439 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 419 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
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
husky
Sets up and manages Husky Git hooks by configuring pre-commit hooks, establishing commit message standards, integrating with linting tools, and ensuring code quality on commits.
create-pr
Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.
fix-github-issue
Analyzes and fixes GitHub issues using a structured approach with GitHub CLI for issue details, implementing necessary code changes, running tests, and creating proper commit messages.
ops-hotfix
Command "ops-hotfix" from christopherlouet/claude-base, covering hotfix agent, request context, objective, workflow and expected output.
work-commit-push-pr
Pointer: Claude Code ships a native /commit-push-pr that owns the commit + push + PR macro. This command adds the foundation's pre-flight gate and convention sources on top — it does not re-implement the macro.