A compliance analysis tool that determines which security responsibilities belong to a cloud provider and which belong to a service operator. IaaS, PaaS, and SaaS are different ways of dividing those responsibilities.

Use it to analyze control inheritance for FedRAMP, NIST, or FISMA at low, moderate, or high baselines across cloud service models.

It clarifies shared responsibility across a provider stack, reducing uncertainty about who must address each control.

inheritance — Command for coding agents by mlunato47: A compliance analysis tool that determines which security responsibilities…

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

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/inheritance.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/inheritance)

Your own site

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

Per session 10 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,262 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.00010	$0.01262
Opus 5	$0.00005	$0.00631
Sonnet 5	$0.00002	$0.00252
Haiku 4.5	$0.00001	$0.00126

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

Security

Grade A, and why

inheritance 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 4d 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:

inheritance — 100% identical, 0 lines differ

grc/commands/inheritance.md · 145 lines

How it starts

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

/grc:inheritance

Model control inheritance based on service model and provider stack.

Usage

/grc:inheritance [framework?] [service-model] [baseline?]

The user can optionally describe their provider stack or specific controls to analyze.

Arguments

framework (optional): fedramp, nist, fisma. Defaults to fedramp.
service-model: iaas, paas, saas, or a description like "SaaS on AWS" or "PaaS on Azure GovCloud"
baseline (optional): low, moderate, high. Defaults to moderate.

Examples

/grc:inheritance fedramp iaas moderate
/grc:inheritance fedramp saas
/grc:inheritance paas on AWS GovCloud
/grc:inheritance fedramp saas high
/grc:inheritance We run a SaaS application on AWS GovCloud (IaaS) using RDS, ECS, and S3

Behavior

When invoked:

Display the Data Sensitivity Notice at the top of every response if the user describes their specific stack (see SKILL.md Data Handling section). If the user only specifies a generic service model (e.g., "iaas"), the notice is not needed.
Read the appropriate reference files:
- skills/grc-knowledge/audits/control-inheritance.md for inheritance patterns by service model
- Framework file from skills/grc-knowledge/frameworks/ for baseline control list
- skills/grc-knowledge/audits/document-section-requirements.md for CRM structure guidance
Generate an inheritance model based on the service model:

a. Control Family Inheritance Table For each of the 20 NIST control families at the specified baseline:
- Expected responsibility designation (Inherited, Shared, Customer, CSP)
- Brief explanation of what's inherited vs. what the customer must implement
- Key controls to pay attention to in each family
b. Detailed Shared Control Breakdown For controls marked as Shared:
- What the underlying provider typically handles
- What the leveraging CSP or customer must handle
- ODP responsibility (who defines parameter values)
- Evidence responsibility (who produces evidence for audit)

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

4d ago First seen · 145 lines · 10 tokens per session scan A 603565da8bca

Subscribe to this mod's changes

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

Legal and compliance Security

review-epo-claims

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

RobThePCGuy/Claude-Patent-Creator · 22 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

inheritance