control-lookup

control-lookup is a command for Claude Code from mlunato47/claude-grc-plugin. It costs 9 tokens per session (2,448 once invoked), scanned A, original, MIT.

A lookup command for finding a security or compliance control by framework, control ID, or keyword. Frameworks are organized sets of requirements, and controls are the individual practices within them.

In plain words
What is it for?
Use it to find controls about topics such as encryption, logging, or multi-factor authentication across NIST, FedRAMP, CMMC, SOC 2, ISO 27001, PCI, HIPAA, CIS, and other supported frameworks.
Why use it?
It avoids searching through large standards manually when you need the meaning or details of one requirement.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grc plugin — 1 skill, 24 commands shipped together

Good fit Use it to find controls about topics such as encryption, logging, or…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/mlunato47/claude-grc-plugin/control-lookup
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.

Clone the repo
git clone --depth 1 https://github.com/mlunato47/claude-grc-plugin

Made for: Claude Code.

Or install grc, the plugin that ships this one along with the rest of its 1 skill, 24 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.

agentmods badge for control-lookup

README.md
[![agentmods](https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/control-lookup.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/control-lookup)
Your own site
<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/control-lookup"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/control-lookup.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,448 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.02448
Opus 5 $0.00005 $0.01224
Sonnet 5 $0.00002 $0.00490
Haiku 4.5 $0.00001 $0.00245

Measured 7d ago against content hash d0e1a380b4e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

control-lookup 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 7d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

grc/commands/control-lookup.md · 158 lines

How it starts

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

/grc:control-lookup

Look up controls by framework and ID or keyword.

Usage

/grc:control-lookup [framework] [id-or-keyword]

Arguments

  • framework: The compliance framework to search. Accepts: nist, fedramp, fisma, cmmc, soc2, iso27001, pci, hipaa, cis, cobit, ccm, gdpr, dod, dow, il2/il4/il5/il6, srg, 20x, cr26, ksi, itar, usml, ddtc
  • id-or-keyword: A control ID (e.g., ac-2, CC6.1, A.8.1) or a keyword (e.g., multi-factor, encryption, logging)

Examples

/grc:control-lookup nist ac-2
/grc:control-lookup soc2 CC6.1
/grc:control-lookup pci 8.3
/grc:control-lookup nist encryption
/grc:control-lookup iso27001 A.8.5
/grc:control-lookup cis 5.2
/grc:control-lookup il5 ac-2
/grc:control-lookup ksi KSI-IAM-APM
/grc:control-lookup itar 120.54

Behavior

When invoked:

  1. Identify the framework from the first argument. Normalize aliases:
    • nist / 800-53 → NIST 800-53 Rev 5
    • fedramp → FedRAMP (NIST 800-53 + FedRAMP parameters)
    • cmmc / 800-171 → CMMC 2.0 / NIST 800-171
    • soc2 / soc → SOC 2 Trust Services Criteria
    • iso / iso27001 / 27001 → ISO 27001:2022
    • pci / pcidss → PCI DSS v4.0.1
    • hipaa → HIPAA Security Rule
    • cis → CIS Controls v8.1
    • cobit → COBIT 2019
    • ccm / csa → CSA CCM v4
    • gdpr → GDPR
    • dod / dow / il2 / il4 / il5 / il6 / srg → DoD/DoW Impact Levels (DISA CSP SRG). Read skills/grc-knowledge/frameworks/dod-impact-levels.md and skills/grc-knowledge/mappings/nist-to-dod-il.md; for the underlying FedRAMP baseline controls also read the OSCAL family JSON as for fedramp. When the argument is a specific IL (e.g., il5), report that level's full composition (baseline + FedRAMP+ + CNSSI 1253 additions).
    • 20x / cr26 / ksi → FedRAMP 20x / Consolidated Rules for 2026. Read skills/grc-knowledge/frameworks/fedramp-20x.md. KSI IDs use the KSI-THEME-KEY scheme (e.g., KSI-IAM-APM); CR26 rule IDs use SET-SUBSET-KEY (e.g., VDR-CSO-DET). For exact current rule/KSI text, fetch the machine-readable sources listed in that file's documentation index rather than answering from the summary alone.
    • itar / usml / ddtc → ITAR (22 CFR 120–130). Read skills/grc-knowledge/frameworks/itar.md. ITAR "IDs" are CFR sections (e.g., 120.54, 126.1) or USML categories (Roman numerals I–XXI) — note the 2022 reorganization renumbered most definitions, and that file's structure table maps old→new section numbers.

Read the full file on GitHub · 158 lines

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.

  1. 7d ago First seen · 158 lines · 9 tokens per session scan A d0e1a380b4e1

Subscribe to this mod's changes

control-lookup is a command published in the GitHub repository mlunato47/claude-grc-plugin (181 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 2,448 once invoked, about $0.0000 per session on Opus 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-30.