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 agentmods add skills/metaschema-framework/claude-plugins/oscal-mappingnpx skills add metaschema-framework/claude-plugins --skill oscal-mappinggit clone --depth 1 https://github.com/metaschema-framework/claude-pluginsWrote 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/metaschema-framework/claude-plugins/oscal-mapping)<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="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.00026 | $0.03176 |
| Opus 5 | $0.00013 | $0.01588 |
| Sonnet 5 | $0.00005 | $0.00635 |
| Haiku 4.5 | $0.00003 | $0.00318 |
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 5d 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 — 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 betweenoscal-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: []
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.
- 5d ago First seen · 412 lines · 26 tokens per session scan A 2cd06543c7d4
oscal-mapping is a skill published in the GitHub repository metaschema-framework/claude-plugins (10 stars, last pushed 6mo 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. 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
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…