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.
npx agentmods add commands/mlunato47/claude-grc-plugin/deviation-requestgit clone --depth 1 https://github.com/mlunato47/claude-grc-pluginWhat 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.00013 | $0.01011 |
| Opus 5 | $0.00006 | $0.00505 |
| Sonnet 5 | $0.00003 | $0.00202 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
deviation-request 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deviation-request — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:deviation-request
Draft deviation requests, risk acceptances, or false positive justifications.
Usage
/grc:deviation-request [framework] [control-id] [reason-type]
Arguments
- framework: The compliance framework
- control-id: The specific control ID requiring deviation
- reason-type: The type of deviation. Accepts:
operational— Operational requirement prevents full implementationfalse-positive— Scanner finding is a false positiverisk-adjustment— Risk is mitigated by compensating controlsvendor-dependency— Remediation depends on vendor actiontechnology-constraint— Technical limitation prevents implementationtemporary— Temporary deviation with planned remediation
Examples
/grc:deviation-request fedramp si-2 vendor-dependency
/grc:deviation-request fedramp ac-7 operational
/grc:deviation-request pci 6.3.3 false-positive
/grc:deviation-request nist sc-28 technology-constraint
/grc:deviation-request fedramp ra-5 temporary
Behavior
When invoked:
-
Identify the framework, control, and reason type from arguments.
-
Read the relevant framework reference and POA&M management reference (
conmon/poam-management.md). -
Draft a deviation request that includes all required elements:
a. Finding identification:
- POA&M ID / Weakness ID
- Control ID and title
- Finding source (scan tool, assessment, etc.)
- Original severity and risk rating
b. Deviation justification (varies by reason type):
- Operational: Why the control cannot be fully implemented, what business process depends on the exception, impact of full implementation
- False positive: Technical evidence that the finding is not a true vulnerability, scanner configuration details, manual verification results
- Risk adjustment: Compensating controls in place, residual risk calculation, why compensating controls adequately mitigate the risk
- Vendor dependency: Vendor ticket/case number, vendor acknowledgment, expected vendor timeline, interim mitigations
- Technology constraint: Technical limitation details, alternatives evaluated, compensating controls
- Temporary: Planned remediation date, milestones, interim mitigations
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.
- 2d ago First seen · 126 lines · 13 tokens per session scan A ca63b59f90ba
deviation-request is a command published in the GitHub repository mlunato47/claude-grc-plugin (180 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 1,011 once invoked, about $0.0001 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.
Other commands, from other repositories
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
au-soci-cirmp
You are an enterprise architect generating a Security of Critical Infrastructure Act 2018 (SOCI Act) / Critical Infrastructure Risk Management Program (CIRMP) governance and evidence pack for an Australian critical infrastructure asset or potentially regulated entity.
au-aescsf
You are an enterprise architect generating an Australian Energy Sector Cyber Security Framework (AESCSF) maturity assessment for an Australian energy-sector project, asset, market interface, OT environment, DER platform, or regulated energy business capability.
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.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
privacy-plan
Privacy / GDPR / APPI / store-label audit — plan only, no policy or SDK edits until approved.