Standards Drift Detection

Standards Drift Detection is a skill for Claude Code from WYRE-AI/msp-claude-plugins. It costs 82 tokens per session (1,767 once invoked), scanned A, original, Apache-2.0.

A skill for finding configuration drift: a change between a system's approved baseline and its current state. It uses standards checks and inspection histories to identify changes that may be intentional or unauthorized.

In plain words
What is it for?
Use it to compare current tenant and infrastructure settings with earlier checks, review detected changes, and separate expected changes from suspicious ones.
Why use it?
It helps detect when security or infrastructure settings have changed after previously meeting a standard, before the change becomes a compliance or operational problem.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Part of the compliance-pack plugin — 3 skills, 3 commands, 3 agents shipped together

Good fit Use it to compare current tenant and infrastructure settings with earlier checks, review detected changes, and separate expected changes from suspicious ones.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wyre-ai/msp-claude-plugins/standards-drift
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.

Any agent
npx skills add WYRE-AI/msp-claude-plugins --skill standards-drift
Clone the repo
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-plugins

Made for: Claude Code.

Or install compliance-pack, the plugin that ships this one along with the rest of its 3 skills, 3 commands, 3 agents.

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

agentmods badge for Standards Drift Detection

README.md
[![agentmods](https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/standards-drift/github.svg)](https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/standards-drift)
Your own site
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/standards-drift"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/standards-drift/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.

agentmods 80×15 button for Standards Drift Detection

Your own site · 80×15
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/standards-drift"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/standards-drift.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,767 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00082 $0.01767
Opus 5 $0.00041 $0.00883
Sonnet 5 $0.00016 $0.00353
Haiku 4.5 $0.00008 $0.00177

Measured 5d ago against content hash 216b8e8f781c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

Standards Drift Detection 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 5d 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.

msp-claude-plugins/compliance-pack/skills/standards-drift/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Standards Drift Detection

Overview

A compliance control that was met last quarter is not guaranteed to still be met today. Tenants change constantly — a conditional access policy gets edited during a troubleshooting session and never reverted, a firewall rule gets loosened for a vendor's "temporary" remote session, a new admin account gets created without MFA during an emergency. None of this shows up unless something actively compares current state against a baseline. That comparison is what this skill covers.

Drift detection has two distinct data sources in this pack's grounding:

  • CIPP standards checks (cipp__list_standards, cipp__run_standards_check, cipp__list_bpa) — these represent MSP-defined or CIS-aligned configuration standards applied to a tenant. A standard that previously passed and now fails is drift. cipp__list_standards shows which standards are assigned to a tenant and their last-known state; cipp__run_standards_check re-evaluates live.
  • Liongard change detection (liongard__detections_list, liongard__detections_get, liongard__timeline_list) — Liongard inspects systems on a schedule and diffs each inspection against the prior one, surfacing detections when tracked properties change. The timeline is the authoritative "what changed and when" record for anything Liongard inspects (network gear, servers, cloud tenants, and whatever else an org has connected inspectors for).

Anti-triggers

  • Running or reading a CIPP standards check — the Report/Alert/Remediate modes, BPA reports, and domain-health results are the connector's own surface; use cipp-standards. This skill decides whether a delta is real drift, whether it was authorized, and how it ranks against other findings.
  • Liongard detection and alert-rule configuration — detection types, severities, alert rules, and custom metrics live in liongard-detections.
  • Inforcer baseline alignment scores — Inforcer computes tenant-versus- baseline drift natively with its own alignment model; use inforcer-baseline-alignment.

Read the full file on GitHub · 88 lines

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. 5d ago First seen · 88 lines · 82 tokens per session scan A 216b8e8f781c

Subscribe to this mod's changes

Standards Drift Detection is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,767 once invoked, about $0.0004 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.