A command for producing executive and technical reports from compliance review materials, including the scope, audit findings, evidence list, and remediation plan.

Use it after a compliance assessment to summarize the review scope, risks, findings, evidence, remediation timeline, and methodology.

It organizes risks, findings, evidence references, and unfinished fixes into one report without claiming that the system is certified compliant.

report — Command for Claude Code by vaquarkhan

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/vaquarkhan/compliance-agent-skills

agentmods

npx agentmods add commands/vaquarkhan/compliance-agent-skills/report

Made for: Claude Code.

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/vaquarkhan/compliance-agent-skills/report/github.svg)](https://agentmods.dev/commands/vaquarkhan/compliance-agent-skills/report)

Your own site

<a href="https://agentmods.dev/commands/vaquarkhan/compliance-agent-skills/report"><img src="https://agentmods.dev/badge/commands/vaquarkhan/compliance-agent-skills/report/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/vaquarkhan/compliance-agent-skills/report"><img src="https://agentmods.dev/badge/commands/vaquarkhan/compliance-agent-skills/report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 437 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00437
Opus 5	$0.00000	$0.00218
Sonnet 5	$0.00000	$0.00087
Haiku 4.5	$0.00000	$0.00044

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

Security

Grade A, and why

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

.claude/commands/report.md · 66 lines

What it actually says

/report — Findings Report

Produce executive and technical compliance reports.

Prerequisites

Scope artifact (/scope)
Audit findings (/audit)
Evidence manifest (/evidence)
Remediation plan (/remediate) if gaps exist

Report structure

1. Executive summary (≤1 page)

Engagement ID, period, frameworks
Overall posture: not assessed / gaps identified / controls operating effectively (never "certified compliant")
Top 3–5 risks by severity
Remediation timeline summary

2. Scope recap

In-scope / out-of-scope systems
Data classifications
Limitations and dependencies

3. Findings detail

ID	Severity	Control	Observation	Recommendation	Status

4. Evidence index

Reference audit-evidence-manifest.yaml artifact IDs — do not embed raw evidence in report body.

5. Remediation tracker

Summary table from /remediate output.

6. Appendices

Control matrix excerpt
Methodology (skills used, MCP tools, sampling approach)

Structured output (recommended)

Copy templates/reports/regulatory-findings-report.yaml to your engagement folder.
Populate from scope, audit, evidence, and remediate artifacts.
Generate Markdown:

python scripts/generate-regulatory-report.py engagement/findings-input.yaml -o engagement/findings-report.md

See docs/regulatory-reports.md and examples/regulatory-reports/ for framework samples (HIPAA, PCI, SOC 2, NIST AI RMF, FERPA/COPPA).

Rules

No raw PHI/PAN in report text
Cite control IDs (HIPAA §, PCI Req, TSC CC)
Include disclaimer: not legal advice; not attestation

Distribution

Classify as Confidential. Use secure channel for external auditors.

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.

10d ago First seen · 66 lines · 0 tokens per session scan A dddb22ee8d10

Subscribe to this mod's changes

report is a command published in the GitHub repository vaquarkhan/compliance-agent-skills (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 437 tokens. 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-31.

Legal and compliance Writing and docs agent-skills ai-agents audit cmmc compliance fedramp

report