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 skills/mick-gsk/drift/drift-commit-pushnpx skills add mick-gsk/drift --skill drift-commit-pushgit clone --depth 1 https://github.com/mick-gsk/driftWhat 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 | $0.00066 | $0.01728 |
| Opus 5 | $0.00033 | $0.00864 |
| Sonnet 5 | $0.00013 | $0.00346 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
drift-commit-push 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 2d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Commit And Push Skill
Use this skill for repository-safe commit and push workflows in Drift.
When To Use
- Prepare a commit after code changes
- Choose the correct conventional commit type
- Check whether a push is allowed
- Verify pre-push gates before pushing to
main - Decide which supporting artifacts must be updated with the code change
Core Rules
- Do not push autonomously. A push requires explicit maintainer approval.
- Never commit blocked paths. Anything under
tagesplanung/is excluded from pushes. - Use conventional commits. Release automation depends on
feat:,fix:, andBREAKING:semantics. - Releases are CI-automated. Do not run manual release flows in normal operation; do not handcraft versioning beyond commit semantics.
- Run lightweight validation before commit; run full validation once per push cycle.
- Do not bypass hooks by default. Environment-variable bypasses are emergency-only and must be justified.
Step 0: Run The Drift Policy Gate
Before preparing a commit or push, run the mandatory admissibility gate for the underlying task. If the task is not admissible, stop instead of committing polished but policy-invalid work.
Use the gate format from .github/instructions/drift-policy.instructions.md.
Step 1: Classify The Change
Choose the commit type from the actual impact:
fix:for bug fixes and regressionsfeat:for new user-visible capabilitiesrefactor:for internal restructuring without behavior changedocs:for documentation-only changestest:for tests-only changeschore:for maintenance workBREAKING:or aBREAKING CHANGE:footer for incompatible changes
If the change touches signals, scoring, output formats, or architecture boundaries, an ADR under docs/decisions/ is required before implementation unless the change is only a bug fix or pure refactoring. Stop and satisfy that requirement before committing.
Step 2: Inspect The Working Tree
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.
- 2d ago First seen · 201 lines · 66 tokens per session scan A 92334d3ed978
drift-commit-push is a skill published in the GitHub repository mick-gsk/drift (14 stars, last pushed 29d ago), licensed MIT. It adds 66 tokens to every session and 1,728 once invoked, about $0.0003 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
truecourse-hooks
Install, configure, or remove the TrueCourse pre-commit hook.
check
Analyze staged git changes with archguardian before committing.
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.
git-commit-push-pr
Commit all changes, push to remote, and open a pull request in one go. Use when the user says "commit push pr", "ship it", "open a pr", or invokes /git-commit-push-pr.
truecourse-analyze
Run TrueCourse architecture analysis on this repository.
git-commit
Git commit message generator that creates conventional commit messages based on code changes.