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/gtapps/claude-code-hermit/docs-driftnpx skills add gtapps/claude-code-hermit --skill docs-driftgit clone --depth 1 https://github.com/gtapps/claude-code-hermitWhat 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.00170 | $0.02325 |
| Opus 5 | $0.00085 | $0.01162 |
| Sonnet 5 | $0.00034 | $0.00465 |
| Haiku 4.5 | $0.00017 | $0.00232 |
Grade A, and why
docs-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 2d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Drift
Verify that documentation tells the truth about either the changes about to ship or the latest version already shipped.
Keep the audit read-only. Do not edit, commit, tag, push, publish, or release until the user explicitly approves specific findings. Even after approval, never commit or publish from this skill.
Invocation
$docs-driftor$docs-drift unreleased— audit every plugin with a non-empty[Unreleased]section.$docs-drift <plugin-slug>— audit that plugin's unreleased changes.$docs-drift latest— audit the latest reachable release of every tagged plugin.$docs-drift latest <plugin-slug>— audit only that plugin's latest release.
Use unreleased mode by default. Treat "latest version", "latest release", or equivalent wording as latest-release mode.
Typical release order, when the sibling skills are installed:
$release-status → $pre-release-review → $docs-drift → $release
Step 1 — Scope plugins and snapshots
Never mix released and unreleased windows in one claim set.
Unreleased mode
Identify plugins whose [Unreleased] section contains non-blank content:
for p in plugins/*/CHANGELOG.md; do
slug=$(basename "$(dirname "$p")")
awk '/^## \[Unreleased\]/{f=1; next} /^## \[/{f=0} f && NF' "$p" | rg -q '.' \
&& echo "$slug"
done
If the user named a plugin, limit scope to that slug after verifying it exists and has unreleased content. If nothing is in scope, stop with:
No unreleased changes in any plugin — nothing to drift-check.
Use the working tree as the documentation snapshot. Keep incidentally noticed older drift separate as pre-existing debt.
Latest-release mode
Start from all plugins/*/CHANGELOG.md slugs, or only the user-named slug.
Resolve each plugin's refs independently:
EMPTY_TREE=$(git hash-object -t tree /dev/null)
for p in plugins/*/CHANGELOG.md; do
slug=$(basename "$(dirname "$p")")
latest=$(git describe --tags --abbrev=0 --match "${slug}--v*" HEAD 2>/dev/null || true)
if [ -z "$latest" ]; then
printf '%s\n' "$slug: skipped (no reachable release tag)"
continue
fi
previous=$(git describe --tags --abbrev=0 --match "${slug}--v*" "${latest}^" 2>/dev/null || true)
printf '%s\n' "$slug latest=$latest previous=${previous:-<empty-tree>}"
done
What ships with it
1 file 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.
- 2d ago First seen · 254 lines · 170 tokens per session scan A d13bc0d2f8e9
docs-drift is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed today), licensed MIT. It adds 170 tokens to every session and 2,325 once invoked, about $0.0009 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…