cipp-alerts skillA
cipp-alerts is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: CIPP's read-only alerting and audit surface: the cross-tenant alert queue, tenant-scoped M365 unified audit log queries, the audit operations worth filtering on during a compromise investigation, and audit lag/retention behavior..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# CIPP Alerts & Audit Logs CIPP raises alerts based on standards violations, anomaly detection, and configured thresholds. The two tools in this skill let you triage the alert queue and pull underlying audit log evidence. ## Anti-triggers - **A CIPP tool is erroring or a background job failed** — that is CIPP's own application log, `cipp_list_logs`, in `cipp-ops`. It is not `cipp_list_audit_logs`, which reads the customer tenant's M365 unified audit log. - **An endpoint or SIEM detection** — a CIPP alert is a configuration or threshold alert about a tenant, never an EDR finding. Use `huntress-incidents`, `blumira-findings`, `sentinelone-alerts`, or `blackpoint-incident-response` depending on which product raised it. - **The forensic snapshot for one compromised user** — `cipp_bec_check` is in `cipp-users`; the audit-log queries here supplement it rather than replace it. - **Why an alert fired at all** — the standard that raised it, and its Report/Alert/Remediate mode, live in `cipp-standards`. ## Tools ### `cipp_list_alert_queue` ``` cipp_list_alert_queue() ``` …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/cipp-alerts@git:20260804.f49efe8mdr add wyre-ai/msp-claude-plugins/cipp-alerts@sha256:48ee4ad72fffa651Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_neqlr3d2v532l74t)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.f49efe8 latest | 2026-08-04 | f49efe8 | 4,413 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 3,598 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 3,629 B | A | view · diff |
| git:20260507.ba09ce6 | 2026-05-07 | ba09ce6 | 3,639 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4413 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wyre-ai/msp-claude-plugins · 46 stars · license Apache-2.0 · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_neqlr3d2v532l74t GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/cipp-alerts GET https://markdownregistry.com/api/v1/blob/48ee4ad72fffa651d0733f927b9129cc689b16c876ceb623a7899aab7900ab29
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.