sar-response

sar-response is a command for Claude Code from mlunato47/claude-grc-plugin. It costs 6 tokens per session (1,246 once invoked), scanned A, original, MIT.

A drafting command for writing structured replies to SAR, or Security Assessment Report, findings—records of issues identified during a security assessment.

In plain words
What is it for?
Use it with FedRAMP, NIST, or FISMA findings to draft a response, disagree with a finding, or view a blank response template.
Why use it?
It provides a consistent response structure for addressing, challenging, or documenting a finding.

Command for Claude Code

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

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

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/sar-response
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, 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.

agentmods badge for sar-response

README.md
[![agentmods](https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/sar-response.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/sar-response)
Your own site
<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/sar-response"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/sar-response.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 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,246 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.01246
Opus 5 $0.00003 $0.00623
Sonnet 5 $0.00001 $0.00249
Haiku 4.5 $0.00001 $0.00125

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

Security

Grade A, and why

sar-response 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 6d 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/sar-response.md · 159 lines

How it starts

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

/grc:sar-response

Help draft structured responses to SAR (Security Assessment Report) findings.

Usage

/grc:sar-response [framework?] [action?]

The user pastes a SAR finding after invoking the command.

Arguments

  • framework (optional): fedramp, nist, fisma. Defaults to fedramp.
  • action (optional):
    • respond (default): Draft a structured response to a finding
    • disagree: Draft a response disagreeing with a finding (false positive or risk acceptance)
    • template: Show the blank response template structure

Examples

/grc:sar-response fedramp
/grc:sar-response fedramp respond
/grc:sar-response fedramp disagree
/grc:sar-response template

Behavior

When invoked:

  1. Display the Data Sensitivity Notice at the top of every response (see SKILL.md Data Handling section). SAR findings may contain system-specific vulnerability details.

  2. Read the appropriate reference files:

    • skills/grc-knowledge/audits/sar-response-patterns.md for response templates and quality checklist
    • skills/grc-knowledge/audits/document-section-requirements.md for POA&M field requirements
    • skills/grc-knowledge/conmon/poam-management.md for severity SLAs
  3. For respond action:

    Analyze the pasted finding and generate a structured response covering:

    a. Acknowledgment

    • Confirm understanding of the finding
    • Note agreement or partial agreement

    b. Root Cause Analysis

    • Suggest root cause categories based on the finding type (operational, documentation, technical)
    • Provide placeholder language the user can customize
    • Avoid suggesting root causes that evaluate security posture

    c. Remediation Plan

    • Suggest specific, actionable remediation steps
    • Include role placeholders for responsible parties
    • Calculate target dates based on severity SLA
    • Suggest granular milestones (not just "remediate")

    d. Interim Mitigations

    • Suggest interim mitigations appropriate to the finding type
    • For Critical/High: emphasize urgency of interim controls

Read the full file on GitHub · 159 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. 6d ago First seen · 159 lines · 6 tokens per session scan A d9f9ffd5be22

Subscribe to this mod's changes

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

Related

Other commands, from other repositories