Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/mick-gsk/drift/drift-release-mandatorygit 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-mandatory)<a href="https://agentmods.dev/instructions/mick-gsk/drift/drift-release-mandatory"><img src="https://agentmods.dev/badge/instructions/mick-gsk/drift/drift-release-mandatory.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.00204 | $0.00204 |
| Opus 5 | $0.00102 | $0.00102 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
drift drift-release-mandatory.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 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.
What it actually says
Release Automation
Vollständige Dokumentation: siehe
drift-release-automation.instructions.md(gleicher Scope).
Diese Datei ist absichtlich knapp und dient nur als Reminder.
Kurzregel: Conventional Commits (feat:, fix:, BREAKING:) verwenden — CI übernimmt Version, Tag, Release und PyPI.
Kein manueller Release-Befehl nötig. Lokaler Fallback nur bei CI-Ausfall: python scripts/release_automation.py --full-release.
See Also
- Release Workflow:
.github/workflows/release.yml - PSR Configuration:
pyproject.toml→[tool.semantic_release] - Detailed Skill:
.github/skills/drift-release/SKILL.md
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 · 19 lines · 204 tokens per session scan A a1d78aba4089
drift drift-release-mandatory.instructions.md is an instructions file published in the GitHub repository mick-gsk/drift (14 stars, last pushed 1mo ago), licensed MIT. It adds 204 tokens to every session, about $0.0010 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
plan-forge version.instructions.md
Version management — Semantic versioning, auto-increment, commit-driven version bumps, release tagging.
plan-forge copilot-instructions.md
Copilot instructions for srnichols/plan-forge, covering instructions for copilot, architecture principles, core principles (non-negotiable), cost estimates and talking to forge-master.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
plan-forge policy.instructions.md
Azure Policy and Initiative compliance — definitions, assignment, compliance state, exemptions, remediation tasks.
plan-forge api-patterns.instructions.md
API patterns for .NET — REST conventions, ProblemDetails, pagination, versioning, error responses.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.