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 progmboy/openprocmon --skill procmongit clone --depth 1 https://github.com/progmboy/openprocmonWrote 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/progmboy/openprocmon/procmon)<a href="https://agentmods.dev/skills/progmboy/openprocmon/procmon"><img src="https://agentmods.dev/badge/skills/progmboy/openprocmon/procmon/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/progmboy/openprocmon/procmon"><img src="https://agentmods.dev/badge/skills/progmboy/openprocmon/procmon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.02968 |
| Opus 5.5 | $0.00032 | $0.01187 |
| Sonnet 5.5 | $0.00016 | $0.00594 |
| Haiku 4.5 | $0.00008 | $0.00297 |
Grade A, and why
procmon 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 1mo 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenProcMon (procmon-cli)
OpenProcMon is a capture-then-analyze tool. A capture records process/file/
registry/network events to a Procmon-compatible .PML file; every analysis
command reads a .PML and prints JSON. The same procmon-cli binary also
serves these as MCP tools (procmon-cli mcp).
Prerequisites
- 64-bit Windows.
procmon-clion PATH. - Live capture needs Administrator (it loads a kernel driver). Analyzing an
existing
.PMLneeds no elevation. Check withprocmon-cli driver-status.
Workflow
- Capture the target's behavior to a
.PML(or open an existing one). - Query the
.PMLwith filters to extract what you need. - Drill in to a specific event for its detail + call stack.
1. Capture
Capture a program and all its children for 10s, launching it first:
procmon-cli capture --name notepad.exe --launch "notepad.exe" --duration 10
--name X(repeatable) targets a process by image name — matches present and future processes of that name.--pid Ntargets a specific instance.- Child processes are followed by default;
--no-childrento disable. --launch "<cmd>"starts the program first so startup is captured.--monitor process,file,registry,networkselects sources (default: all).--duration <secs>and--max-mb <N>bound the capture;--out <path>sets the.PML(default: a temp file).--filter "<expr>"narrows what's recorded (lossy — prefer narrowing at analysis time; same syntax as query below).- Empty
--name/--pidcaptures the whole system. For injection-suspected malware (the payload may run inside an existing process, not a child), capture system-wide and filter afterward.
capture prints the pml_path, a summary, and a sample of events. Re-analyze
that .PML with the commands below.
2. Query — the universal tool
procmon-cli query --pml <file> [--filter "<expr>"] [--group-by <cols>] [--metric <col>] [--limit N]
--filter "<expr>"— a single filter expression (see the Filter syntax section below). One flag expresses AND, OR, NOT and parens.--group-by <Column[,Column...]>— return distinct values + counts (de-duplicated) instead of raw events. Comma-separate for multi-column (e.g.ProcessName,Path). Use it to avoid flooding (distinct files, not 5000 WriteFile rows).--metric <numeric column/field>— roll up sum/avg/min/max + first/last time per group (e.g.--metric NetBytesfor bytes per endpoint). Only with--group-by.- Noise (NTFS metadata, monitoring tools, IRP/FastIO bookkeeping, the tool
itself) is excluded by default; add
--no-noiseto see everything.
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.
- 1mo ago First seen · 230 lines · 80 tokens per session scan A bbaa012c4d97
procmon is a skill published in the GitHub repository progmboy/openprocmon (355 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 2,968 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
Driver Analysis
Windows kernel driver analysis — DriverEntry, dispatch table, IOCTL handlers, vulnerability audit.
notebooklm
Install, authenticate, troubleshoot, and operate Gemini Notebook through the notebooklm-py CLI or typed async Python API. Use for notebook and source management, grounded chat and research, and artifact generation or download when the user mentions Gemini Notebook, notebooklm-py, the notebooklm CLI, or its Python API.…
wxjava-troubleshooter
A troubleshooting guide for WxJava, a Java library used to connect applications to WeChat services. It organizes problems involving setup, access tokens, signatures, payment certificates, callbacks, data conversion, network requests, and multiple accounts.
applicationinsights-web-ts
Instrument browser/web apps with the Application Insights JavaScript SDK (@microsoft/applicationinsights-web). Use for Real User Monitoring (RUM) — page views, clicks, AJAX/fetch dependencies, exceptions, custom events, and browser-side GenAI agent traces correlated to backend OpenTelemetry traces. Covers SDK Loader…
azure-kubernetes-automatic-readiness
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic…
azure-diagnostics
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function…