poam-help

poam-help is a command for Claude Code from nathanimphilipos/synergos-grc. It costs 7 tokens per session (622 once invoked), scanned A, a copy of poam-help, MIT.

A set of governance, risk, and compliance resources covering security frameworks, controls, audits, evidence, continuous monitoring, and operational procedures.

In plain words
What is it for?
Use it for control research, audit preparation, evidence handling, risk and compliance workflows, document review, and cross-framework comparisons.
Why use it?
It gives developers and security teams shared guidance for handling compliance work across several standards and regulations.

Command for Claude Code

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

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

Good fit Use it for control research, audit preparation, evidence handling, risk and compliance workflows, document review, and cross-framework comparisons.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/nathanimphilipos/synergos-grc/poam-help
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/nathanimphilipos/synergos-grc

Made for: Claude Code.

Or install grc, the plugin that ships this one along with the rest of its 1 skill, 27 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 poam-help

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/poam-help"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/poam-help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 622 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 100% copy Near-identical to another mod 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.00007 $0.00622
Opus 5 $0.00003 $0.00311
Sonnet 5 $0.00001 $0.00124
Haiku 4.5 $0.00001 $0.00062

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

Security

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

This is a copy

100% identical to poam-help — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

grc/commands/poam-help.md · 93 lines

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 finding
    • update — Update an existing POA&M entry (milestones, status)
    • close — Close/verify a completed POA&M entry
    • template — Show POA&M entry template with all required fields
    • escalate — Handle overdue or escalated POA&M items
    • deviation — 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:

  1. Identify the action from the argument.

  2. Read the POA&M management reference from conmon/poam-management.md.

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

Read the full file on GitHub · 93 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 · 93 lines · 7 tokens per session scan A ff24b3b542bf

Subscribe to this mod's changes

poam-help is a command published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 6mo 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. It is 100% identical to poam-help, differing in 0 lines, and is treated as a copy.