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/dwarvesf/dwarves-kitnpx agentmods add skills/dwarvesf/dwarves-kit/topology-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/dwarvesf/dwarves-kit/topology-drift)<a href="https://agentmods.dev/skills/dwarvesf/dwarves-kit/topology-drift"><img src="https://agentmods.dev/badge/skills/dwarvesf/dwarves-kit/topology-drift.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00250 | $0.01987 |
| Opus 5 | $0.00125 | $0.00993 |
| Sonnet 5 | $0.00050 | $0.00397 |
| Haiku 4.5 | $0.00025 | $0.00199 |
Grade A, and why
topology-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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topology drift
Maintainer-only, dwarves-kit repo development only: this skill audits the KIT'S OWN
docs/FEATURES.md/docs/workflow-paths.md pair, which only exists in this repo. It
is not something a consumer/adopter repo would ever have a reason to invoke. To
inventory the features of a project the kit is POINTED AT (a migration source, a
codebase you want documented), use /kit:feature-map instead -- see
docs/patterns/audit-loop.md for how the two relate.
Overview
Audit the live feature estate (every command, agent, skill, hook) against the workflow path map and ship fixes as a PR. This is the feature-inventory instance of docs/patterns/audit-loop.md: the generated registry docs/FEATURES.md (SPEC-219) is the machine truth; docs/workflow-paths.md section 5 is the hand-derived path index that drifts when features land or leave. Tier 1 is pure shell; Tier 2 spends model time only on the delta.
The four slots (per the audit-loop pattern)
| Slot | This instance |
|---|---|
| Item set | every row of docs/FEATURES.md plus every line of docs/workflow-paths.md section 5 (both sides enumerate; the diff is the queue) |
| Contract | (a) FEATURES.md is fresh (regenerating changes nothing); (b) every registry row has exactly one path-index line and vice versa, all four kinds; (c) trigger classes agree between the two (secondary, listed not auto-fixed) |
| Evidence class | Tier 1: the repo itself via the generator diff + sed/comm name extraction. Tier 2: a model re-reads only the delta features' definitions to place them on the topology |
| Apply mechanics | FIX on an isolated branch; new features get a path-index line AND a placement on the section 2/3 diagrams; removed features get their line deleted; PR body lists every verdict; UNSURE never auto-resolved |
Process
-
Freshness gate, REFUSE if stale. Regenerate to a temp file and compare:
bash lib/registry/feature-registry.sh generate /tmp/feat-check.md cmp -s /tmp/feat-check.md docs/FEATURES.md || echo STALE
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 · 77 lines · 250 tokens per session scan A e9b9952527af
topology-drift is a skill published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed today), licensed MIT. It adds 250 tokens to every session and 1,987 once invoked, about $0.0013 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-09-04.
Other skills, from other repositories
instructions-management
Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-implement-qc-loop
Run implement and QC in a continuous loop. Direct command-bar dispatch only; do not select for general queries.
sddp-init
Initialize or amend project governance rules. Direct command-bar dispatch only; do not select for general queries.
sddp-plan
Create an implementation plan from the current feature specification. Direct command-bar dispatch only; do not select for general queries.
sddp-systemdesign
Create or refine the canonical software architecture document. Direct command-bar dispatch only; do not select for general queries.