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 agentmods add skills/aj604/toolshed/detecting-doc-driftnpx skills add aj604/toolshed --skill detecting-doc-driftgit clone --depth 1 https://github.com/aj604/toolshedWrote 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/aj604/toolshed/detecting-doc-drift)<a href="https://agentmods.dev/skills/aj604/toolshed/detecting-doc-drift"><img src="https://agentmods.dev/badge/skills/aj604/toolshed/detecting-doc-drift.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 | $0.00069 | $0.04939 |
| Opus 5 | $0.00034 | $0.02469 |
| Sonnet 5 | $0.00014 | $0.00988 |
| Haiku 4.5 | $0.00007 | $0.00494 |
Grade A, and why
detecting-doc-drift 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 4d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detecting Doc Drift
Overview
A doc is a set of claims about the repo; drift is a claim the repo no longer backs. This skill declares the shape of drift detection so it runs the same way every time and can be invoked programmatically to trigger updates — not a one-off prose review.
Two non-negotiables make the output usable by automation:
- A verdict requires evidence. Never mark a claim VERIFIED because doc and code "seem consistent." Verified means you ran the command, opened the line, or matched the grep.
- The result is structured, not prose. Answer in the verdicts shape below. A human summary on top is fine; the artifact is what the engine reads and downstream tooling parses.
REQUIRED SUB-SKILL: Use writing-docs for any fix you propose — every fix must meet
its bar (real output, no aspirational claims, marked+anchored rationale). This skill finds
and classifies drift; writing-docs governs how the correction reads. fixing-docs
consumes the engine report this skill's audit writes — record digests are the handoff, and
mint-approval takes them from the person who selected them. The scheduling-doc-sync skill
wires detect→fix to cron/PR; where a standing policy is committed there, the selection is
derived by policy-mint instead, which is the only door that mints a policy brand.
The audit (run these steps, in order)
The engine owns scope, segmentation, and validation; this skill owns the judgment in the
middle. Every command below is python3 -m doclifecycle … with the plugin's engine/
directory on PYTHONPATH (plugins/doc-lifecycle/engine/README.md covers both spellings).
Every artifact this audit writes — the plan, the verdicts, the report — goes to
${TMPDIR:-/tmp}/, never the work tree: fixing-docs' applier confines a run to its
approval set's paths, so an audit artifact sitting in the tree reads as an unaccounted
change and the apply refuses (apply-working-tree-not-confined). The steps below reuse
that same destination; only the filename changes per artifact.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 270 lines · 69 tokens per session scan A bcead8cd79ca
detecting-doc-drift is a skill published in the GitHub repository aj604/toolshed (2 stars, last pushed 28d ago), licensed MIT. It adds 69 tokens to every session and 4,939 once invoked, about $0.0003 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
cesiumjs-camera
CesiumJS camera control - Camera, flyTo, lookAt, setView, ScreenSpaceCameraController, CameraEventAggregator, flight animation. Use when positioning the camera, creating flyTo animations, constraining user navigation, tracking entities, or converting between screen and world coordinates.
cesiumjs-imagery
CesiumJS imagery layers - ImageryProvider, ImageryLayer, ImageryLayerCollection, WMS, WMTS, Bing, OpenStreetMap, ArcGIS, Mapbox, tile discard policies. Use when adding or swapping base map layers, configuring imagery providers, layering multiple map sources, or creating split-screen imagery comparisons.
cesiumjs-core-utilities
CesiumJS core utilities and networking - Resource, Color, Event, Request, RequestScheduler, error handling, helper functions, feature detection. Use when fetching remote data, managing HTTP requests, working with colors, handling events, debugging errors, or using utility functions like defined, clone, or…