Borrowing it
Nothing to install: this file belongs to apelogic-ai/db-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/apelogic-ai/db-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/apelogic-ai/db-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/apelogic-ai/db-mcp/release)<a href="https://agentmods.dev/skills/apelogic-ai/db-mcp/release"><img src="https://agentmods.dev/badge/skills/apelogic-ai/db-mcp/release.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.00042 | $0.00998 |
| Opus 5 | $0.00021 | $0.00499 |
| Sonnet 5 | $0.00008 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Cut a db-mcp release. Arguments: patch (default), minor, or major.
Step 1 — Determine bump type and compute new version
Parse $ARGUMENTS. If empty or "patch" → patch bump. "minor" → minor bump. "major" → major bump.
Read current version from packages/core/pyproject.toml (project.version field).
Compute the new version by applying the bump:
- patch: X.Y.Z → X.Y.(Z+1)
- minor: X.Y.Z → X.(Y+1).0
- major: X.Y.Z → (X+1).0.0
State the bump type and new version clearly before proceeding.
Step 2 — Ensure we are on main and it is clean
git branch --show-current
git status --short
If not on main, switch to main and pull latest:
git checkout main
git pull origin main
Abort with a clear message if there are uncommitted changes (tracked files only — untracked files are fine). Do NOT stash or discard changes; ask the user to handle them first.
Step 3 — Bump version in two files
Edit packages/core/pyproject.toml: change version = "OLD" → version = "NEW".
Edit packages/core/src/db_mcp/__init__.py: change __version__ = "OLD" → __version__ = "NEW".
Step 4 — Write release notes
Create docs/releases/vNEW.md with the required sections:
# Release vNEW - {Title}— derive a short title from recent commit messages## Overview— one-paragraph summary of what changed## Highlights— bullet list of user-facing changes## New Features/## Bug Fixes— as applicable (omit empty sections)## Files Changed— table of key files and what changed## Testing— test counts and lint status (get counts by running tests or reading recent output)
To understand what changed since the last release, run:
git log $(git describe --tags --abbrev=0 HEAD^)..HEAD --oneline
Then run:
uv run python scripts/release_notes.py prepare NEW
This validates the release notes structure and prepends them into CHANGELOG.md.
Step 5 — Update uv.lock
uv lock
Step 6 — Validate
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 · 131 lines · 42 tokens per session scan A 68f848622e1e
release is a skill published in the GitHub repository apelogic-ai/db-mcp (6 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 998 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.