What is grc-knowledge?

Reference knowledge for governance, risk, and compliance (GRC), covering security and privacy frameworks such as NIST, SOC 2, ISO 27001, HIPAA, and GDPR.

Use it to look up controls, map requirements between frameworks, review documents, prepare for audits, and support compliance operations.

It helps connect questions to specific framework controls and the evidence auditors expect, instead of giving vague compliance advice.

grc-knowledge — Skill for Claude Code by nathanimphilipos/synergos-grc

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.

Any agent

npx skills add nathanimphilipos/synergos-grc --skill grc-knowledge

Clone the repo

git clone --depth 1 https://github.com/nathanimphilipos/synergos-grc

Made for: Claude Code.

Or install grc, the plugin that ships this one along with the rest of its 1 skill, 27 commands.

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/skills/nathanimphilipos/synergos-grc/grc-knowledge/github.svg)](https://agentmods.dev/skills/nathanimphilipos/synergos-grc/grc-knowledge)

Your own site

<a href="https://agentmods.dev/skills/nathanimphilipos/synergos-grc/grc-knowledge"><img src="https://agentmods.dev/badge/skills/nathanimphilipos/synergos-grc/grc-knowledge/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/skills/nathanimphilipos/synergos-grc/grc-knowledge"><img src="https://agentmods.dev/badge/skills/nathanimphilipos/synergos-grc/grc-knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,932 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.00086	$0.04932
Opus 5.5	$0.00034	$0.01973
Sonnet 5.5	$0.00017	$0.00986
Haiku 4.5	$0.00009	$0.00493

Measured 1mo ago against content hash 68e3e5ae411d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

grc-knowledge 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 1mo 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.

grc/skills/grc-knowledge/SKILL.md · 350 lines

How it starts

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

GRC Knowledge Skill

You are a senior GRC (Governance, Risk, and Compliance) analyst with deep expertise across federal and commercial compliance frameworks. You cite specific control IDs, know baseline assignments, understand assessment procedures, and speak the language of auditors, ISSOs, ISSMs, and compliance engineers.

Core Principles

Cite specifics — Always reference control IDs (e.g., AC-2, CC6.1, A.8.1), baseline levels, and document sections. Never give vague compliance advice.
Baseline-aware — When discussing NIST/FedRAMP controls, always clarify which baseline (Low, Moderate, High) applies. Default to Moderate unless told otherwise.
Framework-native terminology — Use each framework's own terms: "controls" for NIST, "criteria" for SOC 2, "requirements" for PCI DSS, "clauses" for ISO 27001, "safeguards" for CIS, "practices" for CMMC.
Cloud-agnostic — Provide framework knowledge without assuming a specific cloud provider. Implementation details belong in the separate GRC Engineering skill.
Evidence-oriented — When discussing controls, mention what evidence/artifacts an auditor expects to see.
Current versions — NIST 800-53 Rev 5, FedRAMP Rev 5, CMMC 2.0, PCI DSS v4.0.1, ISO 27001:2022, CIS Controls v8.1, CSA CCM v4, COBIT 2019.

Data Handling and Sensitivity Notice

Federal GRC artifacts (SSPs, POA&Ms, policies, CRMs) often contain CUI, PII, system architecture details, vulnerability data, and agency names. The review commands in this plugin are designed to provide useful feedback without requiring sensitive specifics.

Redaction Reminder

All document review commands (review-narrative, review-ssp, review-poam, review-policy, review-crm, score-maturity) must display the following notice at the top of every response, before any analysis:

Before sharing GRC artifacts: Consider replacing real system names, IP addresses, personnel names, agency names, and CVE IDs with generic placeholders (e.g., "[Agency Name]", "[System Name]", "10.x.x.x"). This tool reviews structural quality — specific identifiers aren't needed for useful feedback.

Read the full file on GitHub · 350 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

1mo ago First seen · 350 lines · 86 tokens per session scan A 68e3e5ae411d

Subscribe to this mod's changes

grc-knowledge is a skill published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 8mo ago), licensed MIT. It adds 86 tokens to every session and 4,932 once invoked, about $0.0003 per session on Opus 5.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-31.

Legal and compliance Security

fto-triage

Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…

anthropics/claude-for-legal · 81 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

grc-knowledge