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.
npx skills add vinayaklatthe/microsoft-security-skills --skill purview-insider-risk-managementgit clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skillsWrote 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/skills/vinayaklatthe/microsoft-security-skills/purview-insider-risk-management)<a href="https://agentmods.dev/skills/vinayaklatthe/microsoft-security-skills/purview-insider-risk-management"><img src="https://agentmods.dev/badge/skills/vinayaklatthe/microsoft-security-skills/purview-insider-risk-management/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.
<a href="https://agentmods.dev/skills/vinayaklatthe/microsoft-security-skills/purview-insider-risk-management"><img src="https://agentmods.dev/badge/skills/vinayaklatthe/microsoft-security-skills/purview-insider-risk-management.svg" alt="Reviewed on agentmods" width="80" 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.00245 | $0.02026 |
| Opus 5 | $0.00122 | $0.01013 |
| Sonnet 5 | $0.00049 | $0.00405 |
| Haiku 4.5 | $0.00024 | $0.00203 |
Grade A, and why
purview-insider-risk-management 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 9d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Purview Insider Risk Management
Insider Risk Management (IRM) correlates signals from across M365, endpoints, Defender, Entra, and HR systems to surface risky user activity — most importantly intent over time (e.g., the classic "departing employee exfiltrating customer lists 3 weeks before their last day"). It pairs with Adaptive Protection, which dynamically tightens DLP and CA policy on users whose risk score is rising.
When to use
Operationalizing insider risk detection beyond the program-level baseline: policy template selection, HRIS connector setup, alert tuning, case investigation, and Adaptive Protection rollout.
Do not use this skill for outbound DLP authoring (purview-dlp-policy,
purview-advanced-dlp), eDiscovery (purview-ediscovery), or the high-level insider
risk program framing (insider-risk-baseline).
Policy templates — pick by use case
| Template | What it detects |
|---|---|
| Data theft by departing users | Exfil-type activity in the window around resignation/termination (requires HRIS connector) |
| General data leaks | Risky upload/download/share/print regardless of HR signal |
| Data leaks by priority users | Same as above, scoped to executives, M&A team, etc. |
| Data leaks by risky users | Triggered by Adaptive Protection elevated risk level |
| Security policy violations | Defender alerts indicating user circumvention |
| Risky browser usage | Edge-for-Business browsing to risky sites with sensitive content |
| Risky AI usage | Sensitive data sent to non-sanctioned AI apps (paired with Purview AI Hub) |
| Healthcare / patient data misuse (HIPAA scenarios) | EMR access patterns |
| PII unauthorized access (financial) | Sensitive data viewing outside scope |
Approach
-
Get the prerequisites right. Audit (Standard/Premium) on. Purview connectors for the data sources you need. Sensitivity labels and DLP at least baselined.
-
Wire the HRIS connector. Without it, "departing user" templates have no trigger. Workday and SAP SuccessFactors via Microsoft Graph connectors are the common patterns; custom CSV import also supported. Map the resignation date, termination date, job-change date.
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.
- 9d ago First seen · 143 lines · 245 tokens per session scan A 28f79773dfb5
purview-insider-risk-management is a skill published in the GitHub repository vinayaklatthe/microsoft-security-skills (173 stars, last pushed 2mo ago), licensed MIT. It adds 245 tokens to every session and 2,026 once invoked, about $0.0012 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-03.
Other skills, from other repositories
rfp-response-compliance-review
Reviews a draft proposal against the firm's configurable compliance rules — prohibited language, required disclosures, role and positioning boundaries, and procurement-submission requirements. Logs all findings to the Review Findings SharePoint list and annotates the draft document for salesperson and reviewer…
power-automate
Use when operating Microsoft Power Automate cloud flows from code — create, enable, update, list or delete via the Dataverse Web API (workflow table, category 5) with Entra ID OAuth2, plus run-history debugging. NOT designing the flow definition (that is automation-flows), NOT picking a platform by billing model (that…
carta-witness-signatures
Status of witness and spousal-consent signature requests on option grants, RSAs, PIUs — who still needs to sign, and what's awaiting signature, signed, or expired. Covers one award, one company, or a whole portfolio. Read-only.
carta-hmrc-limits
Report a UK company's HMRC EMI/CSOP limit usage. Use when asked how much EMI allowance is left, whether the company is near the £6m EMI limit, who is close to or over their £250k individual limit, CSOP headroom, or whether a planned grant fits.
carta-interaction-reference-core
The non-negotiable half of Carta's AI agent interaction rules — financial precision, data provenance, the AI-computation gate, how to confirm, and trust & safety. Loaded ONCE per conversation, before any response that presents or writes Carta financial data. Sufficient on its own for write flows; a flow that also…
compliance-verifier
Use this agent to validate deployments against GDPR, HIPAA, SOC2, and other regulatory compliance frameworks and generate audit reports.