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 metaschema-framework/claude-plugins --skill using-oscal-cligit 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/using-oscal-cli)<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.
<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>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.00018 | $0.01152 |
| Opus 5.5 | $0.00007 | $0.00461 |
| Sonnet 5.5 | $0.00004 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
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.
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
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 · 184 lines · 18 tokens per session scan A 0606e128b749
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.
using-oscal-cli compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| using-oscal-climetaschema-framework/claude-plugins | Skill | 10 | 8mo ago | CC0-1.0 | A | 18 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 3d ago | MIT | A | 200 | Claude Code, Codex |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 315k | 6d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |