using-oscal-cli

using-oscal-cli is a skill for Claude Code from metaschema-framework/claude-plugins. It costs 18 tokens per session (1,152 once invoked), scanned A, original, CC0-1.0.

Command-line guidance for oscal-cli, a tool for checking and transforming OSCAL documents. OSCAL is a standardized format for describing security controls, assessments, and related information.

In plain words
What is it for?
Use it to validate OSCAL documents, convert their formats, resolve imported profiles into catalogs, and list allowed values.
Why use it?
It helps developers verify that OSCAL files are valid and move them between XML, JSON, and YAML without guessing the command options.

Skill for Claude Code

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

Part of the oscal-tools plugin — 1 skill shipped together

Good fit Use it to validate OSCAL documents, convert their formats, resolve imported profiles into catalogs, and list allowed values.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/metaschema-framework/claude-plugins/using-oscal-cli
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 using-oscal-cli
Clone the repo
git clone --depth 1 https://github.com/metaschema-framework/claude-plugins

Made for: Claude Code.

Or install oscal-tools, the plugin that ships this one along with the rest of its 1 skill.

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 using-oscal-cli

README.md
[![agentmods](https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/using-oscal-cli/github.svg)](https://agentmods.dev/skills/metaschema-framework/claude-plugins/using-oscal-cli)
Your own site
<a href="https://agentmods.dev/skills/metaschema-framework/claude-plugins/using-oscal-cli"><img src="https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/using-oscal-cli/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.

agentmods 80×15 button for using-oscal-cli

Your own site · 80×15
<a href="https://agentmods.dev/skills/metaschema-framework/claude-plugins/using-oscal-cli"><img src="https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/using-oscal-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,152 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.00018 $0.01152
Opus 5.5 $0.00007 $0.00461
Sonnet 5.5 $0.00004 $0.00230
Haiku 4.5 $0.00002 $0.00115

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

Security

Grade A, and why

using-oscal-cli 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-tools/skills/using-oscal-cli/SKILL.md · 184 lines

How it starts

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

Using oscal-cli

The oscal-cli provides tools for validating, converting, and processing OSCAL documents.

Commands Overview

Command Description
validate Check that an OSCAL instance is well-formed and valid
convert Convert OSCAL between formats (XML, JSON, YAML)
resolve-profile Resolve profile imports to produce a catalog
list-allowed-values List allowed value constraints for OSCAL models

Validate

Check that an OSCAL document is well-formed and valid:

oscal-cli validate <file-or-URI>

Options

Option Description
--as <FORMAT> Source format: XML, JSON, or YAML
-c <URL> Additional constraint definitions
-o <FILE> Write SARIF results to file
--sarif-include-pass Include pass results in SARIF output
--disable-schema-validation Skip schema validation
--disable-constraint-validation Skip constraint validation
--path-format <FORMAT> Path format: auto, metapath, xpath, jsonpointer
--threads <count> Parallel constraint validation threads (experimental)

Examples

# Validate any OSCAL document (auto-detects model type)
oscal-cli validate ssp.json

# Validate with explicit format
oscal-cli validate document.xml --as xml

# Output SARIF results
oscal-cli validate catalog.json -o results.sarif

# Add custom constraints
oscal-cli validate ssp.json -c custom-constraints.xml

Convert

Convert OSCAL documents between formats:

oscal-cli convert --to=<FORMAT> <source-file> [destination-file]

Options

Option Description
--to <FORMAT> Target format: XML, JSON, or YAML (required)
--overwrite Overwrite destination if it exists

Examples

# Convert JSON to YAML
oscal-cli convert --to=yaml catalog.json catalog.yaml

# Convert XML to JSON
oscal-cli convert --to=json ssp.xml ssp.json

# Convert to YAML (output to stdout if no destination)
oscal-cli convert --to=yaml profile.json

Read the full file on GitHub · 184 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. 2mo ago First seen · 184 lines · 18 tokens per session scan A 0606e128b749

Subscribe to this mod's changes

using-oscal-cli is a skill published in the GitHub repository metaschema-framework/claude-plugins (10 stars, last pushed 8mo ago), licensed CC0-1.0. It adds 18 tokens to every session and 1,152 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.

Related

using-oscal-cli compared with skills from other repositories

using-oscal-cli next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
using-oscal-climetaschema-framework/claude-pluginsSkill108mo agoCC0-1.0A18Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k3d agoMITA200Claude Code, Codex
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill315k6d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code