drift

A command for detecting structural drift in a codebase over a chosen period. Structural drift means the project’s organization or risk measures have worsened over time.

In plain words
What is it for?
Reviewing changes over 7, 30, or 90 days, or across the full available history, and creating a maintenance punch list.
Why use it?
It turns gradual changes into a ranked list of newly risky files, worsening dimensions, and newly failing rules.

Command

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 commands/rayforcedb/raysense/drift
Clone the repo
git clone --depth 1 https://github.com/RayforceDB/raysense
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 199 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.00023 $0.00199
Opus 5 $0.00012 $0.00100
Sonnet 5 $0.00005 $0.00040
Haiku 4.5 $0.00002 $0.00020

Measured yesterday against content hash a18bfe4d6fea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

claude-plugin/commands/drift.md · 15 lines

What it actually says

Detect structural drift in the project at $1 over the $2 window.

If $1 is empty, treat the project root as the current working directory. If $2 is empty, default the window to 30d. Accepted values: 7d, 30d, 90d, all.

  1. Call raysense_drift with path: $1 and window: $2 (or 30d if not given).
  2. Cross-check with raysense_trend over the same window for any dimension that visibly trended down.

Produce a punch list, ranked: dimensions that worsened most, files that became newly hot, rules that newly tripped. Include the magnitude of each delta.

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. yesterday First seen · 15 lines · 23 tokens per session scan A a18bfe4d6fea

Subscribe to this mod's changes

drift is a command published in the GitHub repository RayforceDB/raysense (11 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 199 once invoked, about $0.0001 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.