grafana/mcp-grafana is a Model Context Protocol server that lets AI clients access and manage Grafana resources such as dashboards. Grafana users can connect it to an MCP client to search, inspect, create, and update dashboards and related data. The catalogue includes an MCP integration, plugin, and skill for operating Grafana through this server.
Borrowing it
Nothing to install: this file belongs to grafana/mcp-grafana. 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/grafana/mcp-grafana/main/.claude/skills/draft-release/SKILL.mdgit clone --depth 1 https://github.com/grafana/mcp-grafanaWrote 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/grafana/mcp-grafana/draft-release)<a href="https://agentmods.dev/skills/grafana/mcp-grafana/draft-release"><img src="https://agentmods.dev/badge/skills/grafana/mcp-grafana/draft-release/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/grafana/mcp-grafana/draft-release"><img src="https://agentmods.dev/badge/skills/grafana/mcp-grafana/draft-release.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.00025 | $0.01511 |
| Opus 5 | $0.00013 | $0.00756 |
| Sonnet 5 | $0.00005 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
draft-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 10d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Release
You are creating a new release for the mcp-grafana project. The user has provided a bump level: major, minor, or patch.
How the release pipeline works
- This skill creates a
release/v*branch with a CHANGELOG.md update and opens a PR - When the PR is merged, the
auto-tag.ymlworkflow automatically creates the git tag - The tag triggers
release.yml(goreleaser → GitHub Release + binaries) anddocker.yml(Docker images + MCP Registry)
Your job is step 1 only. Do NOT create tags manually.
Step 1: Determine the new version
- Get the latest semver tag:
git tag --sort=-version:refname | head -1 - Parse the tag as
vMAJOR.MINOR.PATCHand bump according to the argument:major→ increment MAJOR, reset MINOR and PATCH to 0minor→ increment MINOR, reset PATCH to 0patch→ increment PATCH
- The new version string is
v<MAJOR>.<MINOR>.<PATCH>(e.g.v0.11.0). The previous tag is the "from" ref.
Step 2: Create the release branch
git checkout main
git pull origin main
git checkout -b release/v<NEW_VERSION>
Step 3: Gather and categorize commits
Run:
git log <PREV_TAG>..HEAD --no-merges --format="%H %s"
For each commit, categorize by its conventional commit prefix:
| Prefix | CHANGELOG Section |
|---|---|
feat |
Added |
fix (security-related) |
Security |
fix |
Fixed |
refactor, perf |
Changed |
BREAKING CHANGE or !: |
Removed (or note as breaking in relevant section) |
Skip these commits entirely:
chore(deps)— dependency bumpschorecommits that only touch CI config, GitHub Actions, or similardocscommits that only update README or non-user-facing docstestcommits that only add/fix testscicommits
Step 4: Write human-readable entries
For each significant commit:
- Read the full commit message:
git log <hash> -1 --format="%B" - Extract the PR number from the commit message (look for
(#NNN)in the subject or aPR:line) - Derive the repo URL:
git remote get-url origin→ extracthttps://github.com/<org>/<repo> - Write a concise, human-readable description of the change (not just the commit subject). Focus on what the user gains.
- Format as:
- Description of the change ([#NNN](https://github.com/<org>/<repo>/pull/NNN))
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.
- 10d ago First seen · 176 lines · 25 tokens per session scan A b909f67cc950
draft-release is a skill published in the GitHub repository grafana/mcp-grafana (3,437 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 1,511 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
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.
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.