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.
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/commands/wyre-ai/msp-claude-plugins/drift-report)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/drift-report"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/drift-report.svg" alt="Measured on agentmods" 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.00018 | $0.00982 |
| Opus 5 | $0.00009 | $0.00491 |
| Sonnet 5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
drift-report 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Report
Compare a client's current configuration against the last known-good compliance baseline and report what changed, prioritized by how much each change matters. Omit client to run across the whole portfolio.
Prerequisites
- Conduit MCP Gateway connected (
conduit) - CIPP and/or Liongard connected for the target client(s) — at least one is required to have anything to diff
- A prior baseline is helpful but not required; if none exists, this run establishes one
Steps
- Discover available tools. Call
conduit__search_toolsto confirm which of CIPP, Liongard, and (optionally) a connected PSA are available — drift detection degrades per plane based on what's connected. - Scope the run. If
clientis given, resolve it to its M365 tenant (CIPP) and/or Liongard environment. If omitted, enumerate all clients with at least one compliance-relevant connector (e.g. viacipp__list_tenantsandliongard__environments_list) and run the report for each. - Invoke the
control-drift-reporteragent for the resolved scope. The agent retrieves the last accepted baseline, re-runs live checks (cipp__run_standards_check,liongard__timeline_list/liongard__detections_list), diffs against baseline, and attempts to correlate each change with a PSA ticket if one is connected. - Present the report, prioritized findings first (security-weakening and unauthorized/unconfirmed at the top), followed by lower-priority administrative and tightening drift.
- If portfolio-wide, close with a rollup table ranking clients by number of high-priority findings.
Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
client |
No | — (portfolio-wide) | The client/organization name to check for drift. Omit to run across every client with a compliance-relevant connector. |
Examples
Single client drift check
/compliance-pack:drift-report "Acme Corp"
Portfolio-wide drift sweep
/compliance-pack:drift-report
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.
- 3d ago First seen · 115 lines · 18 tokens per session scan A e3321bdaef3c
drift-report is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 982 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.