What is oscal-mapping?

A document that records relationships between security controls in different compliance frameworks. A crosswalk shows which controls from one standard correspond to, cover, or differ from controls in another.

Use it to map frameworks such as NIST 800-53 and ISO 27001 and support compliance work across multiple standards.

It helps compare frameworks without manually checking every requirement, while also highlighting gaps and overlaps. This model is experimental and may change.

oscal-mapping — Skill for Claude Code by metaschema-framework

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.

Any agent

npx skills add metaschema-framework/claude-plugins --skill oscal-mapping

Clone the repo

git clone --depth 1 https://github.com/metaschema-framework/claude-plugins

Made for: Claude Code.

Or install oscal, the plugin that ships this one along with the rest of its 9 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/oscal-mapping/github.svg)](https://agentmods.dev/skills/metaschema-framework/claude-plugins/oscal-mapping)

Your own site

<a href="https://agentmods.dev/skills/metaschema-framework/claude-plugins/oscal-mapping"><img src="https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/oscal-mapping/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/metaschema-framework/claude-plugins/oscal-mapping"><img src="https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/oscal-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,176 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.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.03176
Opus 5.5	$0.00010	$0.01270
Sonnet 5.5	$0.00005	$0.00635
Haiku 4.5	$0.00003	$0.00318

Measured 2mo ago against content hash 2cd06543c7d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

oscal-mapping 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 2mo 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.

plugins/oscal/skills/oscal-mapping/SKILL.md · 412 lines

How it starts

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

OSCAL Mapping Model

Status: Experimental

The Mapping model is less mature than other OSCAL models. There is a known bug in oscal-cli that prevents full validation of mapping documents. The schema structure documented here is based on direct analysis of the OSCAL JSON schema and liboscal-java implementation. Use with caution and expect potential changes in future OSCAL releases.

The Mapping model defines relationships between controls in different catalogs, enabling crosswalks between security frameworks and supporting gap analysis. Based on NIST IR 8477 set theory relationship mapping.

Related skills:

oscal-catalog - Catalogs being mapped between
oscal-profile - Baselines that may use mapped controls

Purpose

Control mappings:

Define relationships between controls in different frameworks
Enable crosswalks (e.g., NIST 800-53 to ISO 27001)
Support gap analysis for multi-framework compliance
Document equivalence and coverage between standards
Facilitate compliance with multiple frameworks

Document Structure

mapping-collection:
  uuid: <unique-identifier>
  metadata:
    title: "Control Framework Mapping"
    version: "1.0.0"
    oscal-version: "1.1.2"
  provenance:                              # REQUIRED
    method: human                          # human|automation|hybrid
    matching-rationale: semantic           # syntactic|semantic|functional
    status: complete                       # complete|not-complete|draft|deprecated|superseded
    mapping-description: >-               # REQUIRED - describes the mapping purpose
      Description of this mapping's scope and intended use.
  mappings:
    - uuid: mapping-uuid
      source-resource:
        type: catalog                      # REQUIRED: catalog|profile
        href: "source-catalog.json"        # REQUIRED
      target-resource:
        type: catalog                      # REQUIRED: catalog|profile
        href: "target-catalog.json"        # REQUIRED
      maps: []
  back-matter:
    resources: []

Read the full file on GitHub · 412 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.

2mo ago First seen · 412 lines · 26 tokens per session scan A 2cd06543c7d4

Subscribe to this mod's changes

oscal-mapping is a skill published in the GitHub repository metaschema-framework/claude-plugins (10 stars, last pushed 8mo ago), licensed CC0-1.0. It adds 26 tokens to every session and 3,176 once invoked, about $0.0001 per session on Opus 5.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.

Legal and compliance Security

oscal-mapping next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
oscal-mappingmetaschema-framework/claude-plugins	Skill	10	8mo ago	CC0-1.0	A	26	Claude Code
fto-triageanthropics/claude-for-legal	Skill	10.0k	yesterday	Apache-2.0	A	81	Claude Code
legal-holdanthropics/claude-for-legal	Skill	10.0k	yesterday	Apache-2.0	A	68	Claude Code
specification-writingwanshuiyin/Auto-claude-code-research-in-sleep	Skill	19k	2d ago	MIT	A	49	Claude Code
regulatory-research-fallbackHKUDS/OpenSpace	Skill	7.9k	3d ago	MIT	A	20	Claude Code, Codex
terms-of-servicegenspark-ai/genoffice	Skill	12k	yesterday	Apache-2.0	A	32	Claude Code, Codex
x-scorecardx-cmd/x-cmd	Skill	4.7k	10d ago	Apache-2.0	A	57	Claude Code, Codex