cipp-ops skillA
cipp-ops is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: CIPP's own operational layer rather than the tenants it manages: GDAP role definitions and pending invites, the CIPP scheduler, and the ping/version/log endpoints used to diagnose why other CIPP tools fail silently..
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 Operations The meta-layer — tools for managing CIPP itself rather than the tenants it manages. GDAP for the delegation chain, scheduler for recurring jobs, and health/version/log endpoints for verifying CIPP is reachable and functioning. ## Anti-triggers - **"Who did what" inside a customer tenant** — `cipp_list_logs` here is CIPP's own application log, not the M365 unified audit log. The near-identically named `cipp_list_audit_logs` lives in `cipp-alerts`; loading the wrong one is the most common CIPP mis-route. - **Entra role assignments inside a tenant** — GDAP roles are what the *partner* may delegate, a different object from the roles a tenant's own users hold; use `inforcer-identity-governance` or the `m365` plugin. - **Forcing a standards evaluation now** — the CIPP scheduler runs it on a recurrence, but the on-demand call is `cipp_run_standards_check` in `cipp-standards`. ## GDAP ### `cipp_list_gdap_roles` ``` cipp_list_gdap_roles() ``` Returns the GDAP (Granular Delegated Admin Privileges) role definitions available — the AAD roles your CSP relationship can grant to your MSP technicians per-tenant. ### `cipp_list_gdap_invites` ``` …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/cipp-ops@git:20260804.f49efe8mdr add wyre-ai/msp-claude-plugins/cipp-ops@sha256:84b61a044fb41a50Pin 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_cc54bn7pkh7afetk)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.f49efe8 latest | 2026-08-04 | f49efe8 | 5,093 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 4,414 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 4,472 B | A | view · diff |
| git:20260507.ba09ce6 | 2026-05-07 | ba09ce6 | 4,488 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 (5093 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_cc54bn7pkh7afetk GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/cipp-ops GET https://markdownregistry.com/api/v1/blob/84b61a044fb41a50381ddc2c8009de1fc952bc013e5e2d71788dc53177385716
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.