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 skills add marky291/claude-drift --skill drift-checkgit clone --depth 1 https://github.com/marky291/claude-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/skills/marky291/claude-drift/drift-check)<a href="https://agentmods.dev/skills/marky291/claude-drift/drift-check"><img src="https://agentmods.dev/badge/skills/marky291/claude-drift/drift-check.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.00079 | $0.01789 |
| Opus 5 | $0.00039 | $0.00894 |
| Sonnet 5 | $0.00016 | $0.00358 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
drift-check 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClaudeDrift — drift check
Audit every Claude artifact that steers this project and report where it has drifted from the project's actual reality. The source of truth is the codebase you are invoked from. This is done by reasoning, not by a deterministic script — Claude reads the artifacts and the real code and judges drift, via subagents.
Three kinds of drift matter:
- Reference drift — a path/command/script an artifact names no longer exists.
- Context drift — the artifact's description of the architecture, workflow, tech stack, or conventions no longer matches the code, even when every path still resolves. This is the harder, higher-value class.
- Legacy narration (forward-looking drift) — the artifact is accurate but carries superseded-history framing it shouldn't ("Use Laravel Sail (previously Herd)", "X replaced Y", housekeeping "Updated <date>: previously…"). A steering doc should state the current reality only; the fix strips the history while keeping any genuine removal-guard, provenance ref, or "instead of" comparison. The softest class, but it quietly makes every session read migration backstory.
Arguments ($ARGUMENTS):
--user— also audit~/.claudeartifacts (separate, clearly-marked section).--changed— only audit artifacts changed since the last commit (git diff), for cheap re-runs.--forward-only— spotlight only the Legacy narration class: a focused forward-looking cleanup that reports the ⚪ band alone (broken/stale findings are suppressed). Use when the goal is to make artifacts read present-tense, not to chase broken references.--apply— apply accepted fixes without a second prompt.- a path — audit a different project directory instead of
$CLAUDE_PROJECT_DIR.
The target project dir is $ARGUMENTS's path, else $CLAUDE_PROJECT_DIR, else the
current working directory.
Step 1 — Map the Claude flow
Spawn the claude-flow-mapper subagent (Task tool, subagent_type: "claude-flow-mapper") on the project dir (pass --user if given). It returns the
artifact inventory, a projectReality grounding summary, install-state caveats,
a driftLikelihood rating per artifact, and a memorySystems list — the memory
systems it inferred from the project's own artifacts + MCP config (native file
memory under ~/.claude/projects/<proj>/memory/ and/or memory MCP servers). Native
memory files come back as normal artifacts of type: "memory" and are audited like
any other; MCP-backed memory has no files, so its drift is caught when docs that
route to it are audited against the MCP config.
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 · 133 lines · 79 tokens per session scan A 239c79d4fa81
drift-check is a skill published in the GitHub repository marky291/claude-drift (1 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,789 once invoked, about $0.0004 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-31.
Other skills, from other repositories
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Builds a red-capable feedback loop and runs it before hypothesising — complements static code review (which finds bugs by reading) by running actual repros. Use when the user says 'diagnose'/'debug this', or reports something broken/throwing/failing/slow.
issue-debugging
Systematic methodology for issue debugging including root cause analysis, impact mapping, tiered validation plans, and confidence assessment. Use when analyzing bugs, fixing issues, or validating fixes.
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.
ccc-systematic-debugging
Root-cause debugging via the Iron Law: no fix without confirmed root cause. Reproduce → hypothesize → verify → fix. Use when investigating bugs, test failures, or…
debug
Analyze errors and apply fixes. Use when you have an error message, traceback, or failing log to diagnose.
show-me-proof
A skill for collecting concrete proof that a coding task was completed, such as changed files, test commands, logs, and remaining risks.