Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wardawgmalvicious/agent-confignpx agentmods add skills/wardawgmalvicious/agent-config/drift-updateWrote 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/wardawgmalvicious/agent-config/drift-update)<a href="https://agentmods.dev/skills/wardawgmalvicious/agent-config/drift-update"><img src="https://agentmods.dev/badge/skills/wardawgmalvicious/agent-config/drift-update/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.
<a href="https://agentmods.dev/skills/wardawgmalvicious/agent-config/drift-update"><img src="https://agentmods.dev/badge/skills/wardawgmalvicious/agent-config/drift-update.svg" alt="Reviewed on agentmods" width="80" 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.00174 | $0.06763 |
| Opus 5.5 | $0.00070 | $0.02705 |
| Sonnet 5.5 | $0.00035 | $0.01353 |
| Haiku 4.5 | $0.00017 | $0.00676 |
Grade A, and why
drift-update 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift update
Execute the briefs on disk. /drift-audit finds the drift, /drift-handoff
writes it down, and this skill is the third turn: it applies what the briefs
specify, verifies with the steps the briefs supply, and records that it ran.
The briefs are the instruction set. This skill contributes the loop around them — resolution, a staleness gate, triage, checkpointing, and a stamp — not the content of any edit.
Read every brief from disk, every time. Never reconstruct one from the conversation, from memory of an audit, or from a summary, even when this session produced it. The file is the contract; the transcript is not.
Paths below are relative to the repo root. This skill is project scope — it
lives in .claude/skills/, deployed nowhere since 2026-09-09 — so it only
fires in sessions inside this repo.
1. Preconditions and session posture
Fresh session is the intended way to run this. A brief is written to be read cold; running cold is what proves it was written well.
Check whether /drift-audit or /drift-handoff ran in this session. If
either did, this is a warm run. A report that is merely present does not
count: an @-mention or a path argument loads 00-audit-report.md with its
## Audit window and ## Recommended actions intact, but none of the audit
turn's context the limits below exist for. Runs on 2026-09-08 and 2026-09-11
both met this and stamped themselves fresh. Warm is allowed, with two limits:
- Refuse a brief whose targets include
.claude/skills/drift-audit/,.claude/skills/drift-handoff/, or.claude/skills/drift-update/. Editing the skill that produced the briefs, in the session that produced them, is the one case where warm is actually unsound. Name the brief, say why it was skipped, and tell the user to run it from a fresh session. - Cap the run at three briefs. The audit turn is the expensive one; its
fetched sources and artifact sweep are still resident. Apply the first three
eligible briefs, stop, and report the remainder as pending a fresh session.
The cap counts briefs this run applies; one that 4.2 stamps as
already-appliedcosts a grep and an append, so it does not consume the budget. Compaction part-way through an edit is worse than a restart, because a compacted session is a lossy warm one — strictly worse than a cold one.
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 Changed 2a6362608255
- 8d ago Changed 734a6dca21d1
- 10d ago Changed · +17 lines e9c0ceaef073
- 15d ago Changed 02a7e5176660
- 17d ago Changed · +21 lines 8e3e254f3c07
- 18d ago Changed · +21 lines 2170e4dceb6e
- 23d ago Changed · +34 lines f505d9267781
- 24d ago Changed · +37 lines · -32 tokens per session 554265f9c08b
- 1mo ago Changed · +25 lines 19c7c2f131e8
- 1mo ago First seen · 320 lines · 206 tokens per session scan A 331389685329
drift-update is a skill published in the GitHub repository wardawgmalvicious/agent-config (1 stars, last pushed 7d ago), licensed MIT. It adds 174 tokens to every session and 6,763 once invoked, about $0.0007 per session on Opus 5.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
applicationinsights-web-ts
Instrument browser/web apps with the Application Insights JavaScript SDK (@microsoft/applicationinsights-web). Use for Real User Monitoring (RUM) — page views, clicks, AJAX/fetch dependencies, exceptions, custom events, and browser-side GenAI agent traces correlated to backend OpenTelemetry traces. Covers SDK Loader…
azure-kubernetes-automatic-readiness
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic…
azure-diagnostics
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function…
aks-troubleshooting
Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or…
azure-messaging
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue…
aks-gpu-inference
Diagnose Day-2 AKS GPU and KAITO incidents using profile-aware, read-only evidence. WHEN: 'Insufficient nvidia.com/gpu', GPU pod Pending, model-load OOM, DCGM/VRAM, KAITO Workspace not ready, or GPU autoscaling. DO NOT USE FOR: setup (airunway-aks-setup), non-GPU incidents (aks-troubleshooting), standalone VM quota…