deviation-request

deviation-request is a command for coding agents from nathanimphilipos/synergos-grc. It costs 13 tokens per session (1,011 once invoked), scanned A, a copy of deviation-request, MIT.

A command for writing requests to temporarily depart from a compliance rule, accept a known risk, or explain a scanner false alarm. Compliance frameworks are sets of rules used to protect systems and data.

In plain words
What is it for?
Drafting deviation requests for frameworks such as FedRAMP, PCI, and NIST, with reasons such as vendor limits, technical constraints, or temporary exceptions.
Why use it?
It helps document why a specific security or compliance requirement cannot be fully met or does not apply.

Command

Part of the grc plugin — 1 skill, 27 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/nathanimphilipos/synergos-grc/deviation-request
Clone the repo
git clone --depth 1 https://github.com/nathanimphilipos/synergos-grc

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/deviation-request.svg)](https://agentmods.dev/commands/nathanimphilipos/synergos-grc/deviation-request)
Your own site
<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/deviation-request"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/deviation-request.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 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,011 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.01011
Opus 5 $0.00006 $0.00505
Sonnet 5 $0.00003 $0.00202
Haiku 4.5 $0.00001 $0.00101

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

Security

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

This is a copy

100% identical to deviation-request — 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/deviation-request.md · 126 lines

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 implementation
    • false-positive — Scanner finding is a false positive
    • risk-adjustment — Risk is mitigated by compensating controls
    • vendor-dependency — Remediation depends on vendor action
    • technology-constraint — Technical limitation prevents implementation
    • temporary — 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:

  1. Identify the framework, control, and reason type from arguments.

  2. Read the relevant framework reference and POA&M management reference (conmon/poam-management.md).

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

Read the full file on GitHub · 126 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. 5d ago First seen · 126 lines · 13 tokens per session scan A ca63b59f90ba

Subscribe to this mod's changes

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