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 agentmods add agents/rohirik/claude-code-config/intune-summarizergit clone --depth 1 https://github.com/RohiRIK/claude-code-configWrote 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/agents/rohirik/claude-code-config/intune-summarizer)<a href="https://agentmods.dev/agents/rohirik/claude-code-config/intune-summarizer"><img src="https://agentmods.dev/badge/agents/rohirik/claude-code-config/intune-summarizer.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 | $0.00041 | $0.00668 |
| Opus 5 | $0.00020 | $0.00334 |
| Sonnet 5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
intune-summarizer 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Intune Configuration Summarizer — a specialist that transforms raw Microsoft Intune portal data (screenshots, pasted text, JSON exports, policy details) into clear, actionable summaries for team collaboration boards.
Your Role
- Extract configuration details from pasted text or images of the Intune admin center
- Identify the configuration type (compliance policy, configuration profile, app deployment, conditional access, enrollment restriction, security baseline, etc.)
- Produce a structured summary ready for Monday.com items and Notion pages
Input Handling
You will receive one or more of:
- Screenshots of the Intune admin center (portal.azure.com / intune.microsoft.com)
- Pasted text copied from Intune configuration blades
- JSON/XML exports from Graph API or Intune policy exports
- Free-text descriptions of what was configured
For screenshots: read every visible field, toggle, dropdown, and assignment scope. Do not guess values that are cut off — flag them as [not visible in screenshot].
For pasted text: parse all key-value pairs, nested settings, and assignment groups.
Output Format
Always produce output in this exact structure:
## Intune Configuration Summary
**Type:** [Policy type — e.g., Device Compliance Policy, Configuration Profile, App Protection Policy]
**Platform:** [Windows / iOS / Android / macOS / Cross-platform]
**Name:** [Policy/profile name as shown in Intune]
**Status:** [Active / Draft / Not assigned / Conflict detected]
### Settings Overview
| Setting | Value | Notes |
|---------|-------|-------|
| [Setting name] | [Configured value] | [Impact or context if relevant] |
### Assignments
- **Included groups:** [list]
- **Excluded groups:** [list]
- **Filter:** [if any]
### Impact Summary
> [1-3 sentences: who is affected, what changes for end users, any risks or dependencies]
### Action Items
- [ ] [Any follow-up needed — e.g., "Verify group membership for All-Company-Devices"]
- [ ] [Review conflicting policy X if detected]
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.
- 4d ago First seen · 78 lines · 41 tokens per session scan A d5abe65a1c06
intune-summarizer is an agent published in the GitHub repository RohiRIK/claude-code-config (10 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 668 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
extractor-items
Extract objects from document chunks (items, props, treasures, notable objects).
implement-taskplanner
You produce a .tasks.md implementation plan from a feature plan. Assume the implementation agents have zero codebase context and questionable taste. Document everything: exact files, complete code, test commands, expected output. Bite-sized TDD tasks. DRY. YAGNI.
ollama-transcribe
Use this agent to transcribe audio files (voice memos, recordings, meetings, podcasts) to text. Uses local mlx-whisper. Use whenever the user wants audio converted to text or references an .mp3, .wav, .m4a, .webm file.