Borrowing it
Nothing to install: this file belongs to mick-gsk/drift. 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/mick-gsk/drift/main/.github/instructions/drift-release-automation.instructions.mdgit clone --depth 1 https://github.com/mick-gsk/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/instructions/mick-gsk/drift/drift-release-automation)<a href="https://agentmods.dev/instructions/mick-gsk/drift/drift-release-automation"><img src="https://agentmods.dev/badge/instructions/mick-gsk/drift/drift-release-automation.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.00563 | $0.00563 |
| Opus 5 | $0.00282 | $0.00282 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
drift drift-release-automation.instructions.md 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.
What it actually says
Drift Release Automation (python-semantic-release)
Releases werden vollständig durch python-semantic-release in CI verwaltet.
Workflow: .github/workflows/release.yml — läuft bei jedem Push auf main.
Diese Datei ist nur fuer Release-, Commit- und Push-Entscheidungen relevant. Fuer normale Implementierungsarbeit ohne Release-Frage muss sie nicht geladen werden.
Was Agenten tun müssen
- Conventional Commits verwenden — PSR leitet Version aus Commit-Messages ab:
feat: ...→ MINOR (0.x.0)fix: ...→ PATCH (0.0.x)BREAKING CHANGE: .../BREAKING: ...→ MAJOR (x.0.0)
- Tests lokal ausführen vor dem Commit:
make test-fast - Committen — PSR übernimmt nach Push alles Weitere
Was PSR automatisch macht (in CI)
- Analysiert Commits seit letztem Tag
- Berechnet nächste Version (SemVer)
- Aktualisiert
pyproject.toml+CHANGELOG.md - Erstellt Release-Commit (
chore: Release X.Y.Z) - Erstellt Git Tag (
vX.Y.Z) - Erstellt GitHub Release
- Baut Wheel + Sdist → publiziert zu PyPI
Lokaler Fallback (nur bei CI-Ausfall)
python scripts/release_automation.py --full-release
| Fehler | Aktion |
|---|---|
| Tests schlagen fehl | Fehler beheben, dann neu committen. CI startet Release nicht bei fehlenden releasable Commits. |
| PSR findet keine releasable Commits | Normal — kein feat/fix/breaking → kein Release. |
| PyPI Publikation schlägt fehl | GitHub Release existiert. PyPI kann über publish.yml (workflow_dispatch) nachgetriggert werden. |
Konfiguration
- PSR-Config:
pyproject.toml→[tool.semantic_release] - CI-Workflow:
.github/workflows/release.yml - PyPI-Secret:
PYPI_RELEASEim GitHub Environmentpypi
Wichtig: Agenten müssen KEINEN manuellen Release-Befehl mehr ausführen. Conventional Commits + Push auf main genügt.
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 · 55 lines · 563 tokens per session scan A b72e1395799a
drift drift-release-automation.instructions.md is an instructions file published in the GitHub repository mick-gsk/drift (15 stars, last pushed 1mo ago), licensed MIT. It adds 563 tokens to every session, about $0.0028 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.