Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mick-gsk/drift/plugin install driftWrote 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/mick-gsk/drift/drift-release)<a href="https://agentmods.dev/skills/mick-gsk/drift/drift-release"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-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.00046 | $0.00900 |
| Opus 5 | $0.00023 | $0.00450 |
| Sonnet 5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
drift-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 6d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Release Skill (python-semantic-release)
Releases are fully automated via python-semantic-release (PSR) in CI.
Executive Summary
Agents no longer need to run a manual release command.
Workflow: .github/workflows/release.yml runs on every push to main.
PSR parses conventional commits and handles version bump, changelog, tag, GitHub Release, and PyPI publish.
When to Use This Skill
✅ Know this after:
- Feature complete (
feat: ...commit) - Bug fixed (
fix: ...commit) - Breaking change (
BREAKING: ...commit) - All tests pass
- Code committed + pushed to main
The CI release workflow handles everything else automatically.
What Agents Must Do
Step 1: Use Conventional Commits
feat: add new detector for X → MINOR bump (0.X.0)
fix: false alarm in signal Y → PATCH bump (0.0.X)
BREAKING: remove deprecated API → MAJOR bump (X.0.0)
Step 2: Run Tests Locally
make test-fast
Step 3: Commit and Push
PSR in CI handles the rest after push to main.
What PSR Does Automatically (in CI)
- Commits analyzed — from last tag to HEAD
- Version calculated — based on commit types (feat → minor, fix → patch, BREAKING → major)
- Files updated:
pyproject.toml(version field)CHANGELOG.md(new entry)
- Release commit created —
chore: Release X.Y.Z - Git tag created —
vX.Y.Z - GitHub Release created
- Built and published to PyPI
Troubleshooting
| Problem | Solution |
|---|---|
| No release after push | Check commit messages use conventional prefixes (feat:, fix:, BREAKING:). Commits without these don't trigger releases. |
| Tests fail during release | Fix code first. PSR only runs when there are releasable commits. |
| Version looks wrong | Verify recent commit messages. PSR Priority: BREAKING > feat > fix. |
| PyPI publish fails | GitHub Release exists. Re-trigger with publish.yml workflow_dispatch. |
| CI unavailable | Local fallback: python scripts/release_automation.py --full-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.
- 6d ago First seen · 122 lines · 46 tokens per session scan A 876c0e264518
drift-release is a skill published in the GitHub repository mick-gsk/drift (14 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 900 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-30.
Other skills, from other repositories
ship
/ship - Release Pipeline Commander.
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
release-notes
Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release.
open-draft-pr
Prepare local changes for review with an intentional commit, push, and ready PR for fallow. Use when the user wants to publish work, open a PR, or turn local changes into a reviewable branch.
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.