review-poam

review-poam is a command for Claude Code from mlunato47/claude-grc-plugin. It costs 9 tokens per session (1,368 once invoked), scanned A, original, MIT.

A command for reviewing POA&M entries or their structure against security compliance requirements. POA&M means Plan of Action and Milestones: a record of known weaknesses, planned fixes, owners, and progress.

In plain words
What is it for?
Use it to review individual POA&M records or their columns, statuses, and lifecycle model for a selected compliance framework.
Why use it?
It checks whether the information is complete and whether the tracking structure fits frameworks such as FedRAMP, NIST, FISMA, or CMMC.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grc plugin — 1 skill, 24 commands shipped together

Good fit Use it to review individual POA&M records or their columns, statuses, and lifecycle model for a selected compliance framework.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/mlunato47/claude-grc-plugin/review-poam
Install

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.

Clone the repo
git clone --depth 1 https://github.com/mlunato47/claude-grc-plugin

Made for: Claude Code.

Or install grc, the plugin that ships this one along with the rest of its 1 skill, 24 commands.

Wrote 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.

agentmods badge for review-poam

README.md
[![agentmods](https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/review-poam/github.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/review-poam)
Your own site
<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/review-poam"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/review-poam/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.

agentmods 80×15 button for review-poam

Your own site · 80×15
<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/review-poam"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/review-poam.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,368 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.01368
Opus 5 $0.00005 $0.00684
Sonnet 5 $0.00002 $0.00274
Haiku 4.5 $0.00001 $0.00137

Measured 10d ago against content hash a699e862a85a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

review-poam 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 10d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

grc/commands/review-poam.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/grc:review-poam

Review POA&M entries or structure for completeness against FedRAMP and NIST requirements.

Usage

/grc:review-poam [framework?] [action?]

The user pastes their POA&M entry/entries or structure after invoking the command.

Arguments

  • framework (optional): fedramp, nist, fisma, cmmc. Defaults to fedramp.
  • action (optional): entry or structure. Defaults to entry.
    • entry: Reviews individual POA&M entries for field completeness and quality
    • structure: Reviews column headers, status values, and lifecycle model

Examples

/grc:review-poam
/grc:review-poam fedramp entry
/grc:review-poam fedramp structure
/grc:review-poam nist entry

Behavior

When invoked:

  1. Display the Data Sensitivity Notice at the top of every response (see SKILL.md Data Handling section).

  2. Read the appropriate reference files:

    • skills/grc-knowledge/audits/document-section-requirements.md for POA&M field requirements
    • skills/grc-knowledge/conmon/poam-management.md for lifecycle and SLA details
    • Framework file if framework-specific parameters are needed
  3. For entry action — review each POA&M entry against:

    a. Required Fields Check (16+ fields) For each required field, check:

    • Present or Missing
    • If present, quality assessment (specific vs. vague)

    b. Description Quality

    • Is the weakness description specific enough to understand without additional context?
    • Does it identify the root cause or just the symptom?
    • Flag vague descriptions: "improve security", "address finding", "update configuration"

    c. Milestone Quality

    • Are milestones granular (multiple steps) or just "remediate finding"?
    • Do milestone dates progress logically between detection and completion?
    • Is each milestone an actionable step?

    d. SLA Compliance

    • Calculate days between detection date and scheduled completion
    • Compare to severity-based SLA (Critical: 30, High: 30, Moderate: 90, Low: 180)
    • Flag overdue items or items exceeding SLA without deviation request

Read the full file on GitHub · 161 lines

Changes

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.

  1. 10d ago First seen · 161 lines · 9 tokens per session scan A a699e862a85a

Subscribe to this mod's changes

review-poam is a command published in the GitHub repository mlunato47/claude-grc-plugin (181 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,368 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.