What is drift-mcp-repo-ops-usage?

Instructions for using an internal MCP server to check repository operations, such as product health, release readiness, working-tree checks, and audit freshness. MCP is a standard way for an agent to use external tools.

Use them before releases, when checking whether a repository is ready to push, or when verifying that audit records match current changes.

They help agents use the designated checks consistently instead of rebuilding the same checks with manual Git commands or scripts.

How mick-gsk/drift configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/mick-gsk/drift/main/.github/skills/drift-mcp-repo-ops-usage/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/mick-gsk/drift

Made for: Claude Code.

Or install drift, the plugin that ships this one along with the rest of its 31 skills, 17 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mick-gsk/drift/drift-mcp-repo-ops-usage/github.svg)](https://agentmods.dev/skills/mick-gsk/drift/drift-mcp-repo-ops-usage)

Your own site

<a href="https://agentmods.dev/skills/mick-gsk/drift/drift-mcp-repo-ops-usage"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-mcp-repo-ops-usage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mick-gsk/drift/drift-mcp-repo-ops-usage"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-mcp-repo-ops-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,375 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00110	$0.01375
Opus 5	$0.00055	$0.00687
Sonnet 5	$0.00022	$0.00275
Haiku 4.5	$0.00011	$0.00137

Measured 11d ago against content hash ec0c01d90ebf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

drift-mcp-repo-ops-usage 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 11d 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.

.github/skills/drift-mcp-repo-ops-usage/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Drift MCP Repo Ops Usage

Nutze diesen Skill, um den internen MCP-Server in scripts/mcp_product_health_server.py konsistent zu verwenden.

Ziel: Agenten sollen wiederkehrende Repo-Operations direkt per MCP-Tool auslesen, statt dieselben Prüfungen manuell per Terminal zu rekonstruieren.

Wann verwenden

User fragt nach Produktgesundheit oder Adoption/Performance/Stability-Status.
User will eine schnelle Release-Entscheidung (GO/NO_GO) vor Push.
User will wissen, welche Pre-Push-Gates durch den aktuellen Working Tree ausgelöst werden.
User will prüfen, ob §18-Audit-Artefakte gegenüber Signal-Änderungen veraltet sind.

Wann nicht verwenden

Für normale Drift-Codeanalyse im Ziel-Repo: dafür die Drift-MCP-Tools (drift_scan, drift_diff, drift_nudge, ...) verwenden.
Für Azure-, Foundry- oder Cloud-Operations.
Wenn der interne Server nicht registriert ist und der User explizit nur CLI-Workflow möchte.

Vorbedingungen

MCP-Dependency ist installiert:

.venv\Scripts\python.exe -m pip install -e ".[mcp]"

Der Server ist in .vscode/mcp.json registriert und zeigt auf:

command: .venv/Scripts/python.exe (oder passender Python-Pfad)
args: scripts/mcp_product_health_server.py

Bei fehlender Tool-Verfügbarkeit zuerst MCP-Server-Konfiguration reparieren, dann erneut aufrufen.

Tool-Übersicht

drift_product_health(refresh=False)

Liefert Adoption, Stability, Performance aus KPI-Snapshot.
refresh=True nur nutzen, wenn Live-APIs wirklich nötig sind.

drift_release_readiness()

Liefert status: GO|NO_GO, blockers, warnings, agent_instruction.
Prüft u. a. Version-Sync (pyproject.toml, CHANGELOG.md, SECURITY.md, llms.txt) und Blast-Report-Erwartung.

drift_working_tree_context()

Liefert geänderte Bereiche, inferred commit type, getriggerte Gates, empfohlene nächste Aktion.

drift_audit_freshness()

Liefert Freshness der Audit-Artefakte relativ zum letzten src/drift/signals/-Commit.

Read the full file on GitHub · 128 lines

Changes

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.

11d ago First seen · 128 lines · 110 tokens per session scan A ec0c01d90ebf

Subscribe to this mod's changes

drift-mcp-repo-ops-usage is a skill published in the GitHub repository mick-gsk/drift (15 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,375 once invoked, about $0.0006 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.

Git and workflow ai-generated-code architecture cli code-quality copilot

truecourse-hooks

Install, configure, or remove the TrueCourse pre-commit hook.

truecourse-ai/truecourse · 17 tokens

argot-setup

Set argot up for a repository end to end — audit its history, decide what should shape its voice, fit, verify the fit actually catches things, tune the rules its own history says are noisy, and wire the places it runs (pre-write hook, pre-commit, MCP, CI). One sitting, one decision at a time, each proposed with the…

get-tmonier/argot · 129 tokens

release

Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.

AterDev/Perigon.CLI · 34 tokens

feature

Full per-feature pipeline: implement → testloop → evaluator challenge → coder feedback → document → commit.

samibs/skillfoundry · 22 tokens

devops

You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.

samibs/skillfoundry · 6 tokens

ship

/ship - Release Pipeline Commander.

samibs/skillfoundry · 8 tokens

drift: Skill for Claude Code