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 skills add davepoon/buildwithclaude --skill release-checkgit 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/skills/davepoon/buildwithclaude/release-check)<a href="https://agentmods.dev/skills/davepoon/buildwithclaude/release-check"><img src="https://agentmods.dev/badge/skills/davepoon/buildwithclaude/release-check.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.00036 | $0.00363 |
| Opus 5 | $0.00018 | $0.00181 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
release-check 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
Release Check
Runs pre-release verification using the Centinela (QA) agent. This is the highest-stakes checklist in the system.
When to Use This Skill
- Before any release to production
- Before tagging a version
- As a final quality gate after all features are implemented and reviewed
What This Skill Does
- Runs the SIGN IN checklist
- TIME OUT 1 — Documentation and Debt Check: verifies CHANGELOG, TECH_DEBT, specs, and docs
- TIME OUT 2 — Testing and Quality Gate: runs all tests, code health scan, quality verification
- TIME OUT 3 — Security and Release Gate: runs security audit, security verification, release readiness
- Writes release assessment to
docs/reviews/release-check-{version}.md - Issues final verdict: READY FOR RELEASE or BLOCKED (with specific reasons)
How to Use
Basic Usage
/release-check v1.2.0
Example
User: /release-check v2.0.0
Output: A release assessment at docs/reviews/release-check-v2.0.0.md with:
- Documentation completeness check
- Test results and quality gate status
- Security audit summary
- Final verdict with specific blocking reasons if any
Tips
- This is the last line of defense before code reaches users
- A blocked release here prevents issues from reaching production
- Three TIME OUT checkpoints cover docs, quality, and security independently
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 · 49 lines · 36 tokens per session scan A 2ab6e5383b11
release-check is a skill published in the GitHub repository davepoon/buildwithclaude (3,419 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 363 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
03-release-tag
Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.
release-patterns
PR creation, CI/CD validation, merge coordination, and release patterns. Use when creating pull requests, running pre-PR validation, checking CI status, coordinating merges, or managing releases. Do NOT use for routine development commits -- see safe-workflow skill instead.
release-sync
PromptHub release update skill. Use for /update-readme, version bumps, changelog updates, website sync, GUI screenshot/doc refresh, and multilingual release/documentation alignment.
doc-changelog
CHANGELOG maintenance following Keep a Changelog. Trigger when the user wants to document changes or prepare a release.
add-goreleaser-homebrew
Add GoReleaser configuration and a GitHub Actions release workflow to an existing Go CLI project with Homebrew tap publishing. Use when the user says "add goreleaser", "set up goreleaser", "add Homebrew tap publishing", "publish to Homebrew", "set up release workflow", "add release automation for Go", or wants a Go…
release
Cuts the release itself — derives the next semantic version from commits since the last tag, writes plain-English patch notes, previews the plan, then on confirmation creates an annotated tag plus GitHub release, or dispatches the repo's guarded release workflow where production sits behind a workflowdispatch promote…