Borrowing it
Nothing to install: this file belongs to dynatrace-oss/dtctl. 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/dtctl/main/.agents/skills/dtctl-release/SKILL.mdgit clone --depth 1 https://github.com/dynatrace-oss/dtctlWrote 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/dynatrace-oss/dtctl/dtctl-release)<a href="https://agentmods.dev/skills/dynatrace-oss/dtctl/dtctl-release"><img src="https://agentmods.dev/badge/skills/dynatrace-oss/dtctl/dtctl-release.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- 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.00075 | $0.01435 |
| Opus 5 | $0.00037 | $0.00718 |
| Sonnet 5 | $0.00015 | $0.00287 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
dtctl-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 8d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dtctl Release Process (release-please)
dtctl releases use release-please but are triggered manually — nothing releases on ordinary merges to main. There is no manual version bump, no CHANGELOG.md to edit, and no tag to push by hand. The release notes and version are computed from the Conventional Commits since the last release.
How it works
The .github/workflows/release.yml workflow runs only when you trigger it (workflow_dispatch — the "Run workflow" button on the Actions tab, or gh workflow run). A full release is two dispatches with a merge in between:
- Dispatch #1 — the
release-pleasejob inspects the conventional commits since the last release and opens/updates a release PR titled likechore(main): release 0.31.0. That PR:- bumps
.release-please-manifest.json, - bumps the fallback version in
pkg/version/version.go(via the// x-release-please-versionannotation), - and contains the pending release notes (in the PR body).
- bumps
- Merge the release PR once you're happy with the version + notes.
- Dispatch #2 — release-please detects the merged release PR, creates the git tag (
vX.Y.Z) and the GitHub Release with generated notes, andrelease_created == truegates thegoreleaserjob, which builds cross-platform binaries, signs checksums with cosign, generates SBOMs with syft, attaches everything to the release (without overwriting the notes —release.mode: keep-existing), and pushes the updated Homebrew cask todynatrace-oss/homebrew-tap.
⚠️ Don't forget Dispatch #2: merging the release PR alone does not publish anything, because the workflow only runs on manual dispatch.
There is no CHANGELOG.md file in the repo by design — the GitHub Release is the canonical changelog (skip-changelog: true in release-please-config.json).
Version bumps are determined by commit type
| Commit prefix | Bump (pre-1.0) | Example |
|---|---|---|
feat: |
MINOR | 0.30.3 → 0.31.0 |
fix: / perf: |
PATCH | 0.30.3 → 0.30.4 |
feat!: / fix!: or BREAKING CHANGE: footer |
MINOR (pre-1.0) | 0.30.3 → 0.31.0 |
docs: / test: / chore: / ci: / refactor: |
no release on its own | — |
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.
- 8d ago First seen · 83 lines · 75 tokens per session scan A 9bc8a31c6f87
dtctl-release is a skill published in the GitHub repository dynatrace-oss/dtctl (182 stars, last pushed 3d ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,435 once invoked, about $0.0004 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
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
agentplane
Use when a repository uses AgentPlane or the user wants a governed git-native workflow for planning, task execution, verification, and closure.
release
Release Aigon — push to origin, cut a version+tag, or publish to npm. Wraps scripts/ship.js with CHANGELOG draft + dry-run preview. Triggers when the user types "/release", "/push", "/ship", or says "ship a release", "publish a beta", "cut a version", "push to origin", "release X to npm".
aigon-next
Suggest the most likely next workflow action based on current context.
aigon-feature-transfer
Transfer feature from its current agent to a different agent — preserves commits and in-flight work.