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.
git clone --depth 1 https://github.com/mlunato47/claude-grc-pluginWrote 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/commands/mlunato47/claude-grc-plugin/poam-help)<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/poam-help"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/poam-help.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.1 | $0.00007 | $0.00622 |
| Opus 5 | $0.00003 | $0.00311 |
| Sonnet 5 | $0.00001 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
poam-help 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- poam-help — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:poam-help
POA&M (Plan of Action and Milestones) management help and templates.
Usage
/grc:poam-help [action]
Arguments
- action: The POA&M action to get help with. Accepts:
create— Create a new POA&M entry from a findingupdate— Update an existing POA&M entry (milestones, status)close— Close/verify a completed POA&M entrytemplate— Show POA&M entry template with all required fieldsescalate— Handle overdue or escalated POA&M itemsdeviation— Draft a deviation request (redirects to/grc:deviation-request)metrics— POA&M metrics and reporting guidance
Examples
/grc:poam-help create
/grc:poam-help update
/grc:poam-help close
/grc:poam-help template
/grc:poam-help escalate
/grc:poam-help metrics
Behavior
When invoked:
-
Identify the action from the argument.
-
Read the POA&M management reference from
conmon/poam-management.md. -
Present action-specific guidance:
For create:
- Walk through each required field
- Help determine severity based on finding source
- Calculate remediation deadline based on severity (FedRAMP timelines)
- Suggest appropriate milestones
- Show example entry
For update:
- Guidance on milestone updates
- Status transition rules (Open → In Progress → Completed → Closed)
- What constitutes meaningful progress
- Monthly update requirements
For close:
- Verification requirements (re-scan, re-test)
- Evidence needed for closure
- Who approves closure
- Close vs Risk Accepted vs False Positive
For template:
- Full POA&M entry template with all required fields
- Field descriptions and valid values
- FedRAMP-specific fields
- Example completed entry
For escalate:
- When to escalate (approaching deadline, blocked, vendor dependency)
- Escalation path (ISSO → ISSM → CISO → AO)
- Deviation request triggers
- Impact of overdue items on authorization
For metrics:
- Key POA&M metrics: total open, by severity, overdue count, average age, closure rate, reopened rate
- Monthly reporting format
- Trend analysis guidance
- Benchmarks for healthy POA&M posture
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.
- 8d ago First seen · 93 lines · 7 tokens per session scan A ff24b3b542bf
poam-help is a command published in the GitHub repository mlunato47/claude-grc-plugin (181 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 622 once invoked, about $0.0000 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-30.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.