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 Vladick-Pick/business-ontology --skill drift-sweepgit clone --depth 1 https://github.com/Vladick-Pick/business-ontologyWrote 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/vladick-pick/business-ontology/drift-sweep)<a href="https://agentmods.dev/skills/vladick-pick/business-ontology/drift-sweep"><img src="https://agentmods.dev/badge/skills/vladick-pick/business-ontology/drift-sweep/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/vladick-pick/business-ontology/drift-sweep"><img src="https://agentmods.dev/badge/skills/vladick-pick/business-ontology/drift-sweep.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.00035 | $0.01709 |
| Opus 5 | $0.00017 | $0.00855 |
| Sonnet 5 | $0.00007 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
drift-sweep 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 11d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift sweep
Purpose
Drift is caught in two ways: on contact, when work exposes a contradiction, and on cadence, when the model deliberately checks stale cards. drift-flag handles one anchored divergence. drift-sweep is the cadence orchestrator: it finds the cards due for review, checks each against its registered source or current read-only evidence, and routes any real mismatch to drift-flag.
The sweep exists because a model of reality can go stale while still looking valid. A card can keep passing links_validate even after its owner changed, its source-of-truth moved, or a state transition grew a new exception path. The sweep does not make the agent the author of truth; it makes staleness visible before downstream agents and dashboards keep leaning on old claims.
When to use
Use this skill when:
- The configured drift cadence fires.
- A human asks for a review of stale or overdue cards.
- Packaging or publication is about to happen and overdue
next-auditcards need to be checked. synthesize-digestneeds a fresh view of what is overdue, still current, or waiting on human review.
Do not use this skill for a single contradiction encountered during normal work; call drift-flag directly. Do not use it to mine new inputs, register new sources, promote staged changes, or update accepted cards. A sweep can produce proposals and a summary; it cannot commit reality.
Inputs
- Ontology root: the accepted model,
02-source-map.md, open questions, and optional registry. - Cadence date: the date used to compare
next-audit. - Source access: read-only access to the registered sources needed to re-check overdue cards, bounded by each source's read policy.
- Scope limit: optional list of card ids, folders, or source ids to sweep instead of the full ontology.
Procedure
-
Load the accepted model. Read accepted cards only. Staged proposals are visible review material, not truth.
-
Find due cards. Select cards whose
next-auditis before the cadence date, whoselast-reviewedisunknown, or whose source-map entry changed since the last review. Keep the list explicit by card id.
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.
- 11d ago First seen · 105 lines · 35 tokens per session scan A 45d5c27ac78a
drift-sweep is a skill published in the GitHub repository Vladick-Pick/business-ontology (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,709 once invoked, about $0.0002 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
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
open-ontologies
AI-native ontology engineering using 50+ MCP tools backed by an in-memory Oxigraph triple store. Build, validate, query, and govern RDF/OWL ontologies with a generate-validate-iterate loop. Use when building ontologies, knowledge graphs, RDF data, SPARQL queries, BORO/4D modeling, SHACL validation, clinical…
Rare Disease Skills Index
Skills for rare disease case support: ontology-first normalization/retrieval and the clinical genetics consult report format contract (structure + theme). Load the relevant skill file when performing the matching task.
objectstack-platform
Bootstrap, configure, extend, and operate ObjectStack runtimes. Covers project setup (defineStack, drivers, scaffolding), declaring platform capabilities (requires: — which service plugins boot), plugin and service development (PluginContext, DI, kernel hooks like kernel:ready), and operations (CLI commands…
objectstack-automation
Design ObjectStack automation — Flows (visual logic), Triggers, Approvals, state machines, and the jobs (defineJob) / webhooks (defineWebhook) stack collections. Use when the user is adding .flow.ts, wiring an event-driven rule, modelling an approval chain, or building an interactive screen flow / wizard…
objectstack-data
Design ObjectStack data schemas — objects, fields, field conditional rules, relationships, validations, indexes, lifecycle hooks, permissions, row-level security, data lifecycle retention/TTL/rotation, metadata protection locks, and external / federated datasources (defineDatasource) — and the seeds (defineSeed())…