investigate-drift SKILL.md skillA
investigate-drift from confighub/cub-scout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add confighub/cub-scout/investigate-drift@git:20260930.04b45baPins git:20260930.04b45ba in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- confighub/cub-scout
- Path
skills/investigate-drift/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260930.04b45ba, committed Sep 30, 2026
- First version recorded
- May 22, 2026
- Size
- 14,552 bytes
- Repository stars
- 14
- License
- MIT
Use when the user wants to compare live and desired state and inspect available manager and source evidence. Natural phrasing: "why is this Deployment different from the git manifest?", "which recognized manager is recorded for this path?", "controller-drift or interactive-manager evidence?", "compare three-way + attribution for deploy/api". Composes `compare three-way` + `compare drift` + the attribution layer (`cause` / `managerHint` / `gitSource` / `bindingSource`). Do NOT promise who…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# investigate-drift The drift-investigation loop. Live state does not match desired state, so compare the values and inspect available provenance. Composes `compare three-way` (DRY/WET/LIVE) + `compare drift` (file/bundle vs cluster) + attribution (`cause` / `managerHint` / `gitSource` / `bindingSource`). Manager evidence classifies recognized managers; it does not establish write order or human identity. ## When to use Explicit phrasings: - "Why is deploy/api different from the git manifest?" - "Is a recognized interactive manager recorded for this path?" - "Which recognized controller or interactive manager is recorded?" - "controller-drift or manual-edit?" - "Find the field that diverged and show its available manager evidence" - "Compare three-way + attribution for deploy/api in prod" - "The cluster says replicas=1, ConfigHub says 3 — what happened?" Implicit intents: - The user knows there's a divergence; they need the **per-field** detail - The user wants the **cause** classified, not just the diff - The user is planning a *response* (revert to controller / port edit to git / accept manual change) - The user may need to attach the result to a release-gate decision …
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/investigate-drift@sha256:69bc64c07d57ae34The line at the top of this page pins the label git:20260930.04b45ba, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_af3oqkhle2pw4skp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 22, 2026 and Sep 30, 2026, about one every 44 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260930.04b45ba latest | 2026-09-30 | 04b45ba | 14,552 B | A | view · diff |
| git:20260926.4c4b67c | 2026-09-26 | 4c4b67c | 12,960 B | A | view · diff |
| git:20260522.8abb9be | 2026-05-22 | 8abb9be | 12,762 B | A | view · diff |
| git:20260522.095dc05 | 2026-05-22 | 095dc05 | 12,723 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14552 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
confighub/cub-scout · 14 stars · license MIT · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_af3oqkhle2pw4skp GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/investigate-drift GET https://markdownregistry.com/api/v1/blob/69bc64c07d57ae346c91bdbcab7c3241fedc86917f10146adfa3e916d0725f64
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.