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.
git clone --depth 1 https://github.com/nathanimphilipos/synergos-grcWrote 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.
[](https://agentmods.dev/commands/nathanimphilipos/synergos-grc/inheritance)<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/inheritance"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/inheritance.svg" alt="Measured on agentmods" height="20"></a>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.00010 | $0.01262 |
| Opus 5 | $0.00005 | $0.00631 |
| Sonnet 5 | $0.00002 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
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 8d 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.
This is a copy
100% identical to inheritance — 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.
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 tofedramp. - service-model:
iaas,paas,saas, or a description like "SaaS on AWS" or "PaaS on Azure GovCloud" - baseline (optional):
low,moderate,high. Defaults tomoderate.
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.mdfor inheritance patterns by service model- Framework file from
skills/grc-knowledge/frameworks/for baseline control list skills/grc-knowledge/audits/document-section-requirements.mdfor 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)
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.
- 8d ago First seen · 145 lines · 10 tokens per session scan A 603565da8bca
inheritance is a command published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 6mo 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. It is 100% identical to inheritance, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.