GRC Knowledge Plugin

A plugin that turns your AI coding agent into a senior GRC (Governance, Risk, and Compliance) analyst. 72+ reference files covering 15 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:

• 15 compliance frameworks — NIST 800-53, FedRAMP, 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@mlunato47

Or from the CLI:

claude plugin install grc@mlunato47

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

From a Local Directory

Clone the repo and load directly:

git clone https://github.com/mlunato47/claude-grc-plugin.git
claude --plugin-dir ./grc-plugin/grc

Or load alongside other plugins:

claude --plugin-dir ./grc-plugin/grc --plugin-dir ./other-plugin

Once 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")
done

Restart 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

Document Review & Analysis

Operational Workflows

For detailed usage, examples, and tips for every command, see the Usage Guide.

Quick Examples

Look up a control:

/grc:control-lookup fedramp ac-2

Map between frameworks:

/grc:map-controls soc2 CC6.1 to iso27001

Review a control narrative (paste your narrative after the command):

/grc:review-narrative fedramp ac-2 moderate

Check if a change is significant:

/grc:significant-change fedramp Migrating database from EC2 to RDS

Generate a compliance calendar:

/grc:compliance-calendar fedramp,soc2

Generate a tabletop exercise:

/grc:tabletop-scenario ir ransomware saas

Data 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/      # 16 reference files
│           ├── mappings/        # 9 reference files
│           └── tooling/         # 1 reference file
├── GUIDE.md                     # Usage guide
├── LICENSE                      # MIT
└── README.md

How it works:

• SKILL.md is 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-researcher agent 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

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.