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 wardawgmalvicious/agent-config --skill drift-updategit clone --depth 1 https://github.com/wardawgmalvicious/agent-configWrote 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.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.00203 | $0.03707 |
| Opus 5 | $0.00102 | $0.01853 |
| Sonnet 5 | $0.00041 | $0.00741 |
| Haiku 4.5 | $0.00020 | $0.00371 |
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 3d 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 — 289 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.
Repo-relative paths below are relative to the agent-config repo
(C:\Repos\Personal\agent-config), not the session's cwd. ~/.claude/skills
is a junction into that repo, so this skill can fire from a session in any
repo — resolve paths against agent-config regardless of where it fired.
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 a /drift-audit report is present in the conversation — its own
structure (## Audit window plus ## Recommended actions), not a mention of
one. If it is, this is a warm run. Warm is allowed, with two limits:
- Refuse a brief whose targets include
skills/drift-audit/,skills/drift-handoff/, orskills/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.
- 3d ago Changed · +2 lines · -2 tokens per session 49dd1456c33b
- 7d ago First seen · 287 lines · 205 tokens per session scan A b978fde39654
drift-update is a skill published in the GitHub repository wardawgmalvicious/agent-config (1 stars, last pushed today), licensed MIT. It adds 203 tokens to every session and 3,707 once invoked, about $0.0010 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
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
datadog-cli
Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.
graph-query
Query the code graph database to understand component relationships, dependencies, and change impact. Use when the user asks to "find callers", "check dependencies", "what uses this", "show relationships", "find serializers", or when reading code and needing to understand what depends on a component before…
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…
fix-auto
Auto-fix bugs. Observe symptom, find root cause, apply minimal fix, verify, explain in human terms.