Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/oscal-compass-lab/compliance-trestle-skillsnpx agentmods add commands/oscal-compass-lab/compliance-trestle-skills/validate-oscal-packageWrote 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/commands/oscal-compass-lab/compliance-trestle-skills/validate-oscal-package)<a href="https://agentmods.dev/commands/oscal-compass-lab/compliance-trestle-skills/validate-oscal-package"><img src="https://agentmods.dev/badge/commands/oscal-compass-lab/compliance-trestle-skills/validate-oscal-package/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/commands/oscal-compass-lab/compliance-trestle-skills/validate-oscal-package"><img src="https://agentmods.dev/badge/commands/oscal-compass-lab/compliance-trestle-skills/validate-oscal-package.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.00024 | $0.00362 |
| Opus 5 | $0.00012 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
Validate OSCAL Package 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 11d 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.
What it actually says
/oscal-document-workbench:validate-oscal-package
Validate an OSCAL file or Trestle package with available validators and write a validation summary.
How to run
bash plugins/document-transform/oscal-document-workbench/scripts/validate-oscal-package.sh <path> [--output <report.json>] [--allow-partial]
Pass a Trestle workspace directory, an import workspace that contains trestle-workspace/, or one OSCAL JSON file.
The script skips non-OSCAL JSON such as extracted/sections.json.
Arguments
<path>: OSCAL file, Trestle workspace, or import workspace to validate--output <path>: validation report JSON path (default:validation-report.json)--allow-partial: exit 0 when a validator is missing. Default is exit 5 forpartial.
Outputs
reports/validation-report.jsonor the path passed to--output
Exit codes
0: all available validators passed, orpartialwith--allow-partial2: bad arguments or missing target3: a validator reported a structural failure5: required validator missing (partial) and--allow-partialwas not set
Safety notes
- Keep source files unchanged.
- Maintain source traceability for every mapped OSCAL field.
- Mark uncertain mappings as
needs_review. - Do not treat structural validation as an audit opinion.
- Do not commit sensitive customer evidence or real SSPs.
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.
- 11d ago First seen · 43 lines · 24 tokens per session scan A 489867cf0c3a
Validate OSCAL Package is a command published in the GitHub repository oscal-compass-lab/compliance-trestle-skills (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 362 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-30.
Other commands, from other repositories
evidence-examples
Get evidence examples for FedRAMP compliance.
list-ksi
List Key Security Indicators from FedRAMP.
search
Search FedRAMP documentation for compliance guidance.
list-documents
List all FedRAMP FRMR documents.
service-auditor-prep
Generate complete auditor-ready evidence package for SOC 2.
soa-generator
Generate ISO 27001 Statement of Applicability (SOA) with control selection justifications.