Audit Infrastructure As Code
cyberful/cyberful
Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.
Maps infrastructure code (Terraform, Kubernetes, CloudFormation) to compliance controls (ISO 27001, SOC 2, NIST 800-53).
Install Code To Control Mapper
$ npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering code-to-control-mapper --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/grc-engineer/skills/code-to-control-mapper .claude/skills/code-to-control-mapper && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-to-control-mapper" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/grc-engineer/skills/code-to-control-mapper into .claude/skills/code-to-control-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-to-control-mapper", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/grc-engineer/skills/code-to-control-mapperType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering code-to-control-mapper --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/grc-engineer/skills/code-to-control-mapper .agents/skills/code-to-control-mapper && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-to-control-mapper" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/grc-engineer/skills/code-to-control-mapper into .agents/skills/code-to-control-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-to-control-mapper", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering code-to-control-mapper --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/grc-engineer/skills/code-to-control-mapper .cursor/skills/code-to-control-mapper && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-to-control-mapper" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/grc-engineer/skills/code-to-control-mapper into .cursor/skills/code-to-control-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-to-control-mapper", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/GRCEngClub/claude-grc-engineering.git --path plugins/grc-engineer/skills/code-to-control-mapper--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering code-to-control-mapper --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/grc-engineer/skills/code-to-control-mapper .gemini/skills/code-to-control-mapper && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-to-control-mapper" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/grc-engineer/skills/code-to-control-mapper into .gemini/skills/code-to-control-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-to-control-mapper", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install GRCEngClub/claude-grc-engineering code-to-control-mapperInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/grc-engineer/skills/code-to-control-mapper .github/skills/code-to-control-mapper && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-to-control-mapper" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/grc-engineer/skills/code-to-control-mapper into .github/skills/code-to-control-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-to-control-mapper", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering code-to-control-mapper --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/grc-engineer/skills/code-to-control-mapper .opencode/skills/code-to-control-mapper && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-to-control-mapper" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/grc-engineer/skills/code-to-control-mapper into .opencode/skills/code-to-control-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-to-control-mapper", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
code-to-control-mapper- GitHub stars
- 419
- Token cost
- ~524 tokens
- SKILL.md length
- 130 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Maps infrastructure code (Terraform, Kubernetes, CloudFormation) to compliance controls (ISO 27001, SOC 2, NIST 800-53).
- Tasks that involve Infrastructure as code
- SKILL.md covers Quick Commands, Supported Frameworks, Supported IaC Formats and Output Format, plus 2 more sections
- Calls node
- Tasks that involve SOC 2 and security compliance
What it does
Code To Control Mapper is an agent skill from GRCEngClub/claude-grc-engineering. Maps infrastructure code (Terraform, Kubernetes, CloudFormation) to compliance controls (ISO 27001, SOC 2, NIST 800-53). Analyzes IaC files and generates compliance evidence mappings showing which controls are satisfied.
Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Infrastructure as code and SOC 2 and security compliance. It works with AWS CloudFormation, Kubernetes and Terraform. The repository describes itself as: Open-source GRC toolkit from the GRC Engineering Club. Claude Code plugins for evidence collection, SCF crosswalks, multi-framework gap reports, OSCAL workflows.
When your agent uses it
- Tasks that involve Infrastructure as code
- Tasks that involve SOC 2 and security compliance
Example prompts
- “/code-to-control-mapper”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Glob, Write, Edit
What it can do on your machine
Read from SKILL.md and the folder at commit 784fd9a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGlobWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Code To Control Mapper loads about 524 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 130 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Glob, Write, Edit
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 130 words (~524 tokens).
“Maps infrastructure-as-code (IaC) files to specific compliance framework controls. Translates technical implementations into audit-ready compliance evidence.”
- name
- code-to-control-mapper
- allowed-tools
- Bash, Read, Glob, Write, Edit
Files
Just SKILL.md in plugins/grc-engineer/skills/code-to-control-mapper of GRCEngClub/claude-grc-engineering.
Open the folder on GitHubat commit 784fd9a
Compare with similar skills
Code To Control Mapper next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code To Control Mapper this skillGRCEngClub/claude-grc-engineering | 419 | — | ~524 | Automated safety check: Notes | Custom licence | |
| Audit Infrastructure As Codecyberful/cyberful | 135 | — | ~649 | Automated safety check: Pass | AGPL-3.0 | |
| Iac CheckovAgentSecOps/SecOpsAgentKit | 220 | 1 repos | ~4.6k | Automated safety check: Pass | Custom licence | |
| Implementing Infrastructure As Code Security Scanningmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Iac Security ReviewOWASP/secure-agent-playbook | 187 | — | ~694 | Automated safety check: Pass | CC-BY-4.0 | |
| Iac Securityhardw00t/ai-security-arsenal | 104 | — | ~2.4k | Automated safety check: Pass | None |
Similar skills
Iac Checkov
AgentSecOps/SecOpsAgentKit
Infrastructure as Code (IaC) security scanning using Checkov with 750+ built-in policies for Terraform, CloudFormation, Kubernetes, Dockerfile, and ARM templates.
Implementing Infrastructure As Code Security Scanning
mukul975/Anthropic-Cybersecurity-Skills
Implements automated security scanning for Infrastructure as Code using Checkov, tfsec, and KICS to detect misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts, plus…
Iac Security Review
OWASP/secure-agent-playbook
Security review of Infrastructure-as-Code (Terraform, Kubernetes, CloudFormation).
Iac Security
hardw00t/ai-security-arsenal
Infrastructure-as-Code security scanning router for Terraform, CloudFormation, Kubernetes manifests, Helm, ARM/Bicep.
Checking Infrastructure Compliance
jeremylongshore/tons-of-skills-marketplace
Execute use when you need to work with compliance checking. An agent skill from jeremylongshore/tons-of-skills-marketplace.
More from GRCEngClub/claude-grc-engineering
All 12 skills in this repoTrust Center Builder
GRCEngClub/claude-grc-engineering
Builds and deploys a serverless trust center that publishes a company's compliance posture, with gated access to audit reports and an admin dashboard.
GRC Report Context Bootstrap
GRCEngClub/claude-grc-engineering
Checks that plugins, collected findings and history exist before a GRC /report command runs, and walks the user through setup instead of producing an empty report.
Draw.io Diagram Generator
GRCEngClub/claude-grc-engineering
Generates draw.io diagrams as native .drawio files, including GRC workflows and control maps, with optional PNG, SVG or PDF export that stays editable.
Academic Research Companion
GRCEngClub/claude-grc-engineering
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing, feedback, and publication.
Access Review Triage
GRCEngClub/claude-grc-engineering
Helps you triage a quarterly user access review from an Okta, Azure AD, AWS IAM, GitHub, or generic CSV/JSON export.
Audit Ready PR Reviewer
GRCEngClub/claude-grc-engineering
Reviews pull requests for compliance regressions. An agent skill from GRCEngClub/claude-grc-engineering.
Related
Works with
Categories
Questions about Code To Control Mapper
What does Code To Control Mapper do?
Maps infrastructure code (Terraform, Kubernetes, CloudFormation) to compliance controls (ISO 27001, SOC 2, NIST 800-53). Code To Control Mapper is an agent skill from GRCEngClub/claude-grc-engineering. Maps infrastructure code (Terraform, Kubernetes, CloudFormation) to compliance controls (ISO 27001, SOC 2, NIST 800-53).
When should I use Code To Control Mapper?
Code To Control Mapper fits situations like: tasks that involve Infrastructure as code; tasks that involve SOC 2 and security compliance.
How do I install Code To Control Mapper in Claude Code?
Run `npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a claude-code`. Or copy the skill folder (plugins/grc-engineer/skills/code-to-control-mapper in GRCEngClub/claude-grc-engineering) into .claude/skills/code-to-control-mapper in your project. Claude Code loads it when a task matches its description.
How do I install Code To Control Mapper in Codex?
Run `npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a codex`. Or copy the skill folder (plugins/grc-engineer/skills/code-to-control-mapper in GRCEngClub/claude-grc-engineering) into .agents/skills/code-to-control-mapper in your project. Codex loads it when a task matches its description.
Can I use Code To Control Mapper in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GRCEngClub/claude-grc-engineering --skill code-to-control-mapper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-to-control-mapper, .gemini/skills/code-to-control-mapper, .github/skills/code-to-control-mapper and .opencode/skills/code-to-control-mapper in your project.
What does Code To Control Mapper need to run?
Going by SKILL.md and its folder, Code To Control Mapper needs the command-line tools its instructions call (node). Its frontmatter pre-approves these tools: Bash, Read, Glob, Write, Edit.
Does Code To Control Mapper access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Code To Control Mapper safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Code To Control Mapper use?
Code To Control Mapper has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Code To Control Mapper use?
About 524 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Code To Control Mapper?
Skills that share tags, products or a category with Code To Control Mapper: Audit Infrastructure As Code (cyberful/cyberful, 135 stars), Iac Checkov (AgentSecOps/SecOpsAgentKit, 220 stars), Implementing Infrastructure As Code Security Scanning (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Iac Security Review (OWASP/secure-agent-playbook, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code To Control Mapper?
GRCEngClub (a GitHub organization) maintains it in GRCEngClub/claude-grc-engineering, which has 419 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 4, 2026.
Source: GRCEngClub/claude-grc-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.