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/using-oscal-clinpx skills add metaschema-framework/claude-plugins --skill using-oscal-cligit clone --depth 1 https://github.com/metaschema-framework/claude-pluginsWhat 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 | $0.00018 | $0.01152 |
| Opus 5 | $0.00009 | $0.00576 |
| Sonnet 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 2d 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.
- 2d 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 6mo 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. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.