Borrowing it
Nothing to install: this file belongs to dynatrace-oss/dynatrace-managed-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/dynatrace-oss/dynatrace-managed-mcp/main/.github/prompts/release.prompt.mdgit clone --depth 1 https://github.com/dynatrace-oss/dynatrace-managed-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/commands/dynatrace-oss/dynatrace-managed-mcp/release)<a href="https://agentmods.dev/commands/dynatrace-oss/dynatrace-managed-mcp/release"><img src="https://agentmods.dev/badge/commands/dynatrace-oss/dynatrace-managed-mcp/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/commands/dynatrace-oss/dynatrace-managed-mcp/release"><img src="https://agentmods.dev/badge/commands/dynatrace-oss/dynatrace-managed-mcp/release.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.00000 | $0.00261 |
| Opus 5 | $0.00000 | $0.00130 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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 yesterday.
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 Instructions
When preparing a release, follow these steps to ensure everything is in order:
- Go to the main branch and pull the latest changes. If dependencies changed, run
npm ci. - Ask the user what the new version number should be. It should follow semantic versioning, but it may have a suffix for release candidates.
- Work on a release branch, typically named
chore/prepare-release-<version>. - Create a new section in CHANGELOG.md for the version below "Unreleased Changes".
- Move all entries from "Unreleased Changes" to this new section.
- Update the version number in
package.json,server.json(bothversionandpackages[].version), andplugin.json.mcp.jsonhas no version field and needs no change. - Run
npm install --package-lock-onlyto sync the lock file. - Run
npm run version:checkto confirm every manifest agrees. See RELEASE.md. - Let the user verify the release notes and version number before proceeding.
- Commit the changes with a message like
chore(release): prepare for <version> 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.
- yesterday First seen · 20 lines · 0 tokens per session scan A baabd6a979ba
release is a command published in the GitHub repository dynatrace-oss/dynatrace-managed-mcp (28 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 261 tokens. 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-07.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.