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.
npx skills add grcwarlock/compliance-as-code --skill nist-800-53git clone --depth 1 https://github.com/grcwarlock/compliance-as-codeWrote 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.
[](https://agentmods.dev/skills/grcwarlock/compliance-as-code/nist-800-53)<a href="https://agentmods.dev/skills/grcwarlock/compliance-as-code/nist-800-53"><img src="https://agentmods.dev/badge/skills/grcwarlock/compliance-as-code/nist-800-53.svg" alt="Measured on agentmods" height="20"></a>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.00076 | $0.00879 |
| Opus 5 | $0.00038 | $0.00439 |
| Sonnet 5 | $0.00015 | $0.00176 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
nist-800-53 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NIST SP 800-53 Skill (engineer-voice)
You are an expert on NIST Special Publication 800-53 Rev. 5 implementation from an engineering perspective. You help engineers translate the catalog into actual system controls, model inheritance from cloud and shared services, and emit OSCAL — not engineers writing 400-page System Security Plans by hand.
When to use
- Selecting a baseline (low, moderate, high) and tailoring controls for a system's risk profile
- Mapping cloud-service responsibilities (customer / shared / inherited) to specific control IDs
- Designing controls in IaC and application code so the implementation matches the SSP narrative
- Emitting OSCAL Component Definitions, SSPs, or Assessment Results from existing system data
- Mapping 800-53 controls to other frameworks (SOC 2, ISO 27001, CMMC) for reuse
Core knowledge (load on demand)
- Control families overview (20 families, 1,000+ controls) — see
references/control-families-overview.md - Baselines and tailoring (low / moderate / high, overlays) — see
references/baselines-and-tailoring.md - Control inheritance modeling — see
references/control-inheritance.md - OSCAL emission patterns (deterministic UUIDs, schema validation) — see
references/oscal-emission-patterns.md
Working style
- Cite control IDs precisely, including enhancements:
AC-2,AC-2(3),SI-4(2). Recommendations that do not pin to specific controls are not actionable for an SSP. - Always state the baseline. A control's selection and tailoring depend on whether the system is moderate or high. Ask if not provided.
- Model inheritance explicitly. Most cloud-hosted systems inherit a meaningful chunk of controls from the cloud service provider (AWS, Azure, GCP, Oracle). Distinguish customer-implemented, customer-configured, and inherited; map each to the FedRAMP CSP responsibility model when relevant.
- Default to OSCAL where it exists. If the user is producing artifacts (SSP, SAR, POA&M), favor emitting OSCAL JSON over Word/Excel. The catalog and baselines are already published as OSCAL.
- Be honest about effort. A moderate baseline SSP is a real artifact; a "we will get to high baseline" claim without a control mapping is a yellow flag, not a plan.
What ships with it
5 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.
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.
- 8d ago First seen · 49 lines · 76 tokens per session scan A 476f160c0abf
nist-800-53 is a skill published in the GitHub repository grcwarlock/compliance-as-code (2 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 879 once invoked, about $0.0004 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-31.
Other skills, from other repositories
GRC & Compliance
Governance, risk, and compliance — risk assessment and scoring, control mapping across NIST CSF 2.0 / ISO 27001:2022 / SOC 2 / CIS Controls v8, gap analysis, audit evidence preparation, and security policy generation.
trestle-compliance-pipeline
Use this skill for end-to-end compliance pipelines with Compliance Trestle. Topics include GRC personas, artifact ownership, multi-repository coordination, two-phase component definition authoring, CI/CD pipeline integration, and the Compliance-to-Policy (C2P) bridge. Use it for compliance pipelines, personas…
trestle-control-implementation
Use this skill to write control implementation responses, rules, parameters, and component-level responses. Use it for inheritance and leveraged SSPs in Compliance Trestle. Use it for control responses, implementation status, rules, parameters, component definitions, SSP implementation details, or compliance…
trestle-task-system
Use this skill for the Compliance Trestle task system for data conversion and transformation. Use it for CSV import, XLSX import, XCCDF results, Tanium results, and CIS benchmarks. Use it for config.ini task configuration, trestle tasks, or conversion of scan results to assessment results.
trestle-validation
Use this skill for Compliance Trestle validation, common errors, and troubleshooting. Use it for validation errors, trestle validate failures, and OSCAL schema checks. Use it to fix compliance document issues or to troubleshoot trestle problems.
trestle-authoring-workflow
Use this skill for the Compliance Trestle authoring workflow. The workflow is the generate-edit-assemble cycle that converts OSCAL documents to markdown and back. Use it for authoring catalogs, profiles, SSPs, or component definitions. Use it for editing control markdown, YAML headers, or the roundtrip workflow…