Borrowing it
Nothing to install: this file belongs to dbt-labs/dbt-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dbt-labs/dbt-mcp/main/.claude/skills/release-dbt-mcp/SKILL.mdgit clone --depth 1 https://github.com/dbt-labs/dbt-mcpWrote 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/dbt-labs/dbt-mcp/release-dbt-mcp)<a href="https://agentmods.dev/skills/dbt-labs/dbt-mcp/release-dbt-mcp"><img src="https://agentmods.dev/badge/skills/dbt-labs/dbt-mcp/release-dbt-mcp/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/skills/dbt-labs/dbt-mcp/release-dbt-mcp"><img src="https://agentmods.dev/badge/skills/dbt-labs/dbt-mcp/release-dbt-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00324 |
| Opus 5 | $0.00009 | $0.00162 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
release-dbt-mcp 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 11d 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
- Initiate the
Create release PRGitHub workflow. Use theautofor thebumpinput. Don't set theprereleaseinput. - Wait for this to start and then poll the status of this running workflow.
- Once it finishes successfully, approve & squash merge (
gh pr merge --squash --admin) the PR that was created. This repo does not allow merge commits. This is an autogenerated PR, so it is okay to bypass CI. This is the only case that bypassing CI is okay. - Merging this PR will kick off the
Release dbt-mcpworkflow. - Wait for this to start and then poll the status of this running workflow. When the workflow waits for GitHub environment approval, open the page with
open <url> - Ask the user to continue once they have approved the GitHub environment.
- Once the user continues, continue polling the status of the
Release dbt-mcpworkflow. - When that workflow has finished successfully. Ensure that the new version of dbt-mcp is on PyPI by checking the JSON API at
https://pypi.org/pypi/dbt-mcp/json(the HTML page is JS-rendered and won't work with WebFetch). - Report to the user the status of all GitHub workflows that ran and the status of the release.
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.
- 11d ago First seen · 15 lines · 18 tokens per session scan A 7d8348f4d1a8
release-dbt-mcp is a skill published in the GitHub repository dbt-labs/dbt-mcp (603 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 324 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-08-30.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…