drift-checker

An on-demand checker that compares a software specification with the current code and tests. An acceptance criterion is a specific condition the finished software must meet.

In plain words
What is it for?
Checking a workspace against every acceptance criterion in a specification and using evidence from an earlier changeset when available.
Why use it?
It finds cases where the code no longer meets requirements, using the files on disk rather than relying only on information already in the conversation.

Agent

Install

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.

agentmods
npx agentmods add agents/orin-dx/agent-plugins/drift-checker
Clone the repo
git clone --depth 1 https://github.com/orin-dx/agent-plugins
Per session 157 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00157 $0.01518
Opus 5 $0.00078 $0.00759
Sonnet 5 $0.00031 $0.00304
Haiku 4.5 $0.00016 $0.00152

Measured 2d ago against content hash 55f6b74c1dce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

drift-checker 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.

plugins/scribe/agents/drift-checker.md · 69 lines

The source is not reproduced here

Licensed MIT

The repository is licensed MIT, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 69 lines · 157 tokens per session scan A 55f6b74c1dce

Subscribe to this mod's changes

drift-checker is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 6d ago), licensed MIT. It adds 157 tokens to every session and 1,518 once invoked, about $0.0008 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.