GRC Knowledge Plugin
A plugin that turns your AI coding agent into a senior GRC (Governance, Risk, and Compliance) analyst. 75+ reference files covering 17 frameworks, 24 slash commands, and deep domain knowledge for federal and commercial compliance work.
Works with: Claude Code, OpenCode
What It Does
Load this plugin and Claude gains expertise in:
- 17 compliance frameworks — NIST 800-53, FedRAMP Rev5, FedRAMP 20x/CR26, DoD/DoW Impact Levels (IL2–IL6, DISA Cloud SRG), FISMA, CMMC, SOC 2, ISO 27001, PCI DSS, HIPAA, CIS Controls, COBIT, CSA CCM, GDPR, SLSA, OSCAL, and NIST Rev 4→5 transition
- Cross-framework mapping — Map any control to any other framework through NIST 800-53 as the hub
- Document review — Feed it SSP narratives, POA&Ms, policies, CRMs and get structural quality feedback with 0-5 maturity scoring
- Operational workflows — Significant change analysis, inheritance modeling, SAR responses, compliance calendars, tabletop exercises
It cites specific control IDs, knows baseline assignments, understands assessment procedures, and speaks the language of auditors, ISSOs, and compliance engineers.
Install
From a Plugin Marketplace (Recommended)
Add the marketplace and install:
/plugin marketplace add mlunato47/claude-grc-plugin
/plugin install grc@mlunato47Or from the CLI:
claude plugin install grc@mlunato47You can install at different scopes:
claude plugin install grc@mlunato47 # User scope (all projects)
claude plugin install grc@mlunato47 --scope project # Project scope (shared via git)
claude plugin install grc@mlunato47 --scope local # Local onlyFrom a Local Directory
Clone the repo and load directly:
git clone https://github.com/mlunato47/claude-grc-plugin.git
claude --plugin-dir ./grc-plugin/grcOr load alongside other plugins:
claude --plugin-dir ./grc-plugin/grc --plugin-dir ./other-pluginOnce loaded, type /grc: to see all available commands.
OpenCode
You can ask OpenCode to self-install by telling it:
> Fetch and follow the instructions at https://raw.githubusercontent.com/mlunato47/claude-grc-plugin/main/.opencode/INSTALL.md
Or install manually:
# Clone
git clone https://github.com/mlunato47/claude-grc-plugin.git ~/.config/opencode/grc
# Symlink plugin, skills, and commands
mkdir -p ~/.config/opencode/plugins ~/.config/opencode/skills ~/.config/opencode/commands
ln -s ~/.config/opencode/grc/.opencode/plugins/grc.js ~/.config/opencode/plugins/grc.js
ln -s ~/.config/opencode/grc/grc/skills/grc-knowledge ~/.config/opencode/skills/grc-knowledge
for cmd in ~/.config/opencode/grc/grc/commands/*.md; do
ln -s "$cmd" ~/.config/opencode/commands/$(basename "$cmd")
doneRestart OpenCode. Commands are available as /grc-control-lookup, /grc-map-controls, etc.
Commands
> Note: In Claude Code, commands use /grc:command-name. In OpenCode, commands use /grc-command-name.
Framework & Controls
| Command | Purpose | |---------|---------| | /grc:control-lookup | Look up controls by framework and ID or keyword | | /grc:map-controls | Map controls between any two frameworks | | /grc:conmon-guide | Continuous monitoring guidance by topic | | /grc:audit-prep | Audit preparation checklists by audit type | | /grc:poam-help | POA&M creation, templates, and metrics | | /grc:gap-analysis | Structured gap analysis worksheets | | /grc:ssp-section | Draft SSP narrative language by control family | | /grc:deviation-request | Draft deviation/risk acceptance documentation |
Document Review & Analysis
| Command | Purpose | |---------|---------| | /grc:review-narrative | Review SSP control narratives — Five W's, ODPs, 0-5 maturity score | | /grc:review-ssp | Validate SSP structure against FedRAMP template | | /grc:review-poam | Check POA&M entries for field completeness and SLA compliance | | /grc:review-policy | Review policy structure, control coverage, and language quality | | /grc:review-crm | Review CRM coverage, responsibility clarity, and common gaps | | /grc:score-maturity | Score control implementation maturity 0-5 with next-level guidance | | /grc:evidence-checklist | Generate audit evidence prep checklists (no user content needed) |
Operational Workflows
| Command | Purpose | |---------|---------| | /grc:significant-change | Analyze if a system change is "significant" per FedRAMP | | /grc:inheritance | Model control inheritance by service model (IaaS/PaaS/SaaS) | | /grc:sar-response | Draft structured responses to SAR findings | | /grc:compliance-calendar | Generate recurring compliance activity calendar | | /grc:boundary-guidance | Authorization boundary definition guidance | | /grc:tabletop-scenario | Generate IR/CP tabletop exercise scenarios | | /grc:multi-framework | Analyze overlap and gaps across multiple frameworks | | /grc:oscal-guide | OSCAL structure, readiness, and conversion guidance | | /grc:rev5-transition | NIST 800-53 Rev 4 to Rev 5 transition mapping |
For detailed usage, examples, and tips for every command, see the Usage Guide.
Quick Examples
Look up a control:
/grc:control-lookup fedramp ac-2Map between frameworks:
/grc:map-controls soc2 CC6.1 to iso27001Review a control narrative (paste your narrative after the command):
/grc:review-narrative fedramp ac-2 moderateCheck if a change is significant:
/grc:significant-change fedramp Migrating database from EC2 to RDSGenerate a compliance calendar:
/grc:compliance-calendar fedramp,soc2Generate a tabletop exercise:
/grc:tabletop-scenario ir ransomware saasData Sensitivity
GRC artifacts often contain CUI, PII, system architecture, and vulnerability data. This plugin is designed to be useful without requiring sensitive specifics:
- Document review commands display a redaction reminder before every response
- All feedback is structural — "your narrative is missing the frequency component" not "your system is insecure"
- No security posture judgment — the plugin assesses document quality, never system security
- Safe to use with placeholders — replace real names/IPs/agencies with
[Agency Name],[System Name],10.x.x.x
Reference-only commands (evidence-checklist, compliance-calendar, tabletop-scenario, oscal-guide, rev5-transition, multi-framework) don't process user content and skip the reminder.
Architecture
├── .claude-plugin/
│ └── marketplace.json # Claude Code marketplace catalog
├── .opencode/
│ ├── INSTALL.md # OpenCode self-install instructions
│ └── plugins/
│ └── grc.js # OpenCode plugin (injects skill context)
├── grc/ # Claude Code plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin metadata
│ ├── agents/
│ │ └── grc-researcher.md # Read-only research agent
│ ├── commands/ # 24 slash commands
│ │ ├── control-lookup.md
│ │ ├── map-controls.md
│ │ └── ...
│ └── skills/
│ └── grc-knowledge/
│ ├── SKILL.md # Core skill definition (loaded into context)
│ ├── audits/ # 14 reference files
│ ├── conmon/ # 6 reference files
│ ├── frameworks/ # 18 reference files
│ ├── mappings/ # 10 reference files
│ └── tooling/ # 1 reference file
├── GUIDE.md # Usage guide
├── LICENSE # MIT
└── README.mdHow it works:
SKILL.mdis loaded into Claude's context and provides the core GRC analyst persona, framework quick reference, and response guidelines- Slash commands in
commands/define the behavior, arguments, and output format for each command - Reference files in
skills/grc-knowledge/contain deep domain knowledge that commands read on demand - The
grc-researcheragent provides a read-only research interface for complex cross-reference queries - NIST 800-53 serves as the universal mapping hub — any framework maps to any other through NIST
Frameworks Covered
| Framework | Version | Reference File | |-----------|---------|---------------| | NIST 800-53 | Rev 5 | frameworks/nist-800-53.md | | FedRAMP | Rev 5 | frameworks/fedramp.md | | FedRAMP 20x | CR26 (June 2026) | frameworks/fedramp-20x.md | | DoD/DoW Impact Levels | CSP SRG V1R7 (2026) | frameworks/dod-impact-levels.md | | FISMA | Current | frameworks/fisma.md | | CMMC | 2.0 | frameworks/cmmc.md | | SOC 2 | Current | frameworks/soc2.md | | ISO 27001 | 2022 | frameworks/iso-27001-27002.md | | PCI DSS | v4.0.1 | frameworks/pci-dss-v4.md | | HIPAA | Current | frameworks/hipaa.md | | CIS Controls | v8.1 | frameworks/cis-controls-v8.md | | COBIT | 2019 | frameworks/cobit-2019.md | | CSA CCM | v4 | frameworks/csa-ccm-v4.md | | GDPR | Current | frameworks/gdpr.md | | SLSA | v1.2 | frameworks/slsa.md | | OSCAL | 1.1.2 | frameworks/oscal-reference.md | | NIST Rev 4→5 | Transition | frameworks/nist-rev4-to-rev5.md | | Supply Chain (SR) | Rev 5 | frameworks/supply-chain-srm.md |
Contributing
Contributions welcome. The main areas where help is needed:
- Framework updates — Control catalogs change. If a framework publishes a new version, the corresponding reference file needs updating.
- New framework mappings — Adding mappings for frameworks not yet covered.
- Command improvements — Better output formats, additional review criteria, new operational workflows.
- Reference accuracy — If you spot an incorrect control ID, wrong baseline assignment, or outdated parameter value, please open an issue or PR.
Adding a new command
1. Create commands/your-command.md following the pattern of existing commands 2. If the command needs reference data, create a file in the appropriate skills/grc-knowledge/ subdirectory 3. Update skills/grc-knowledge/SKILL.md — add reference navigation entry 4. Update agents/grc-researcher.md — add new reference files to the available list
Adding a new framework
1. Create skills/grc-knowledge/frameworks/your-framework.md 2. Create skills/grc-knowledge/mappings/nist-to-your-framework.md (map through NIST hub) 3. Update the Framework Quick Reference table in SKILL.md 4. Update framework aliases in commands/control-lookup.md and commands/map-controls.md
License
MIT — see LICENSE.
Disclaimer
This plugin provides GRC domain knowledge for documentation and compliance workflow assistance. It does not constitute legal, security, or compliance advice. The plugin assesses document structure and completeness — it does not evaluate whether a system is actually secure or compliant. Always consult qualified GRC professionals and your authorizing official for authorization decisions.
