A command for drafting descriptions of control families in a System Security Plan, a document that explains how a system meets security requirements. It supports frameworks such as NIST, FedRAMP, and CMMC.

Use it to draft access-control, incident-response, identity, system-and-communications-protection, or other control-family sections for a named framework.

Security plans contain many controls, enhancements, parameters, and required statements. This helps organize the relevant requirements into a draft section.

ssp-section — Command for coding agents by mlunato47: A command for drafting descriptions of control families in…

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.

agentmods

npx agentmods add commands/mlunato47/claude-grc-plugin/ssp-section

Clone the repo

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

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

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/ssp-section.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/ssp-section)

Your own site

<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/ssp-section"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/ssp-section.svg" alt="Measured on agentmods" height="20"></a>

Per session 5 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,016 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00005	$0.01016
Opus 5	$0.00003	$0.00508
Sonnet 5	$0.00001	$0.00203
Haiku 4.5	$0.00001	$0.00102

Measured 5d ago against content hash 0ebe987bf137, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ssp-section 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 5d 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:

ssp-section — 100% identical, 0 lines differ

grc/commands/ssp-section.md · 111 lines

How it starts

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

/grc:ssp-section

Draft SSP (System Security Plan) control family descriptions.

Usage

/grc:ssp-section [framework] [control-family]

Arguments

framework: The compliance framework. Primarily nist, fedramp, or fisma (SSP is an RMF artifact). Also supports cmmc for NIST 800-171 security plans.
control-family: The control family ID or name (e.g., ac, access-control, ir, incident-response).

Examples

/grc:ssp-section fedramp ac
/grc:ssp-section nist ir
/grc:ssp-section fedramp ia
/grc:ssp-section cmmc access-control
/grc:ssp-section fedramp sc

Behavior

When invoked:

Identify the framework, baseline, and control family from arguments. Default to FedRAMP Moderate if no baseline specified.
Read the OSCAL family JSON for the complete control list and parameter definitions (use the Read tool — do NOT use Bash, Python, or jq to extract data):
- For nist: read skills/grc-knowledge/oscal/nist-800-53-rev5/{family}.json
- For fedramp: read skills/grc-knowledge/oscal/fedramp-moderate-rev5/{family}.json
- Extract all controls, enhancements, parameters (ODPs), and statement parts from the OSCAL data
- Use parameter values from the OSCAL data to populate FedRAMP-specific ODP values in narratives
- Read .parts[] | select(.name == "assessment-objective") to ensure the narrative addresses every testable objective — each leaf objective's .prose describes what an assessor will verify, so the narrative must cover it
- ID normalization: AC-2 → ac-2, AC-2(1) → ac-2.1
Read the framework reference file from skills/grc-knowledge/frameworks/ for additional narrative context, audit expectations, and cross-framework guidance.
For each control in the family (at the appropriate baseline), draft SSP narrative language following the standard format:

SSP Narrative Structure (per control):
- What: The control objective and what is being implemented
- Who: Responsible roles and teams
- How: Implementation details — mechanisms, tools, processes
- When: Frequency of the activity (if applicable)
- Where: System boundary applicability

Read the full file on GitHub · 111 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.

5d ago First seen · 111 lines · 5 tokens per session scan A 0ebe987bf137

Subscribe to this mod's changes

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

Legal and compliance Security

deps-audit

Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.

wshobson/agents · 23 tokens

riskreview

The user invoked the /riskreview facade command from the risk-review-pipeline pack.

inclusionAI/Avernet · 11 tokens

review-epo-claims

Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.

RobThePCGuy/Claude-Patent-Creator · 22 tokens

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.

avelikiy/great_cto · 53 tokens

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…

tractorjuice/arc-kit · 35 tokens

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.

tractorjuice/arc-kit · 33 tokens