trestle-oscal-models

trestle-oscal-models is a skill for Claude Code from oscal-compass-lab/compliance-trestle-skills. It costs 63 tokens per session (2,044 once invoked), scanned A, original, Apache-2.0.

A reference for OSCAL’s seven document models and how they connect. OSCAL is a standard for representing security controls, system plans, assessments, results, and remediation information.

In plain words
What is it for?
Use it to understand OSCAL model relationships, choose the right document type, and follow the flow from security controls through assessment results to remediation tracking.
Why use it?
It clarifies which model to use and how catalogs, profiles, component definitions, SSPs, assessments, and POA&Ms fit together.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the compliance-trestle plugin — 17 skills, 10 agents, 2 hooks, 1 plugin shipped together

Good fit Use it to understand OSCAL model relationships, choose the right document type, and follow the flow from security controls through assessment results to remediation tracking.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oscal-compass-lab/compliance-trestle-skills/trestle-oscal-models
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 oscal-compass-lab/compliance-trestle-skills --skill trestle-oscal-models
Clone the repo
git clone --depth 1 https://github.com/oscal-compass-lab/compliance-trestle-skills

Made for: Claude Code.

Or install compliance-trestle, the plugin that ships this one along with the rest of its 17 skills, 10 agents, 2 hooks, 1 plugin.

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 trestle-oscal-models

README.md
[![agentmods](https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/trestle-oscal-models/github.svg)](https://agentmods.dev/skills/oscal-compass-lab/compliance-trestle-skills/trestle-oscal-models)
Your own site
<a href="https://agentmods.dev/skills/oscal-compass-lab/compliance-trestle-skills/trestle-oscal-models"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/trestle-oscal-models/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 trestle-oscal-models

Your own site · 80×15
<a href="https://agentmods.dev/skills/oscal-compass-lab/compliance-trestle-skills/trestle-oscal-models"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/trestle-oscal-models.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,044 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.00063 $0.02044
Opus 5 $0.00032 $0.01022
Sonnet 5 $0.00013 $0.00409
Haiku 4.5 $0.00006 $0.00204

Measured 12d ago against content hash 7bba543a6035, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

trestle-oscal-models 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 12d 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.

skills/trestle-oscal-models/SKILL.md · 181 lines

How it starts

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

OSCAL Model Types in Trestle

The 7 OSCAL Model Types

Model Type CLI Name Directory Description
Catalog catalog catalogs/ Set of security controls. Example: NIST 800-53
Profile profile profiles/ Selection and change of controls from catalogs
Component Definition component-definition component-definitions/ How a component implements controls
System Security Plan system-security-plan system-security-plans/ Full system security documentation
Assessment Plan assessment-plan assessment-plans/ Plan for assessment of security controls
Assessment Results assessment-results assessment-results/ Results of a security assessment
POA&M plan-of-action-and-milestones plan-of-action-and-milestones/ Remediation tracking

Model Relationships

Catalog (controls)
    ↓ imports
Profile (selects + modifies controls)
    ↓ resolved profile catalog
Component Definition (how components implement controls)
    ↓ combined
System Security Plan (complete system documentation)
    ↓ assessed by
Assessment Plan → Assessment Results → POA&M

The Catalog → Profile → SSP Chain

  1. A Catalog defines controls. Example: NIST 800-53 has about 1000 controls.
  2. A Profile imports controls from catalogs or profiles. It selects a subset. It can change parameters.
  3. A Resolved Profile Catalog is the effective control set after profile changes.
  4. A Component Definition describes how specific components address controls.
  5. An SSP combines a profile and component definitions into implementation documentation.

Profile Imports

A profile can import from:

  • One or more catalogs
  • One or more other profiles
  • A mix of catalogs and profiles

Each import selects specific controls. An import can change parameters. An import can add content.

Common OSCAL Fields

All models share:

  • uuid: Unique identifier
  • metadata: Title, version, last-modified, oscal-version, roles, parties
  • back-matter: Resources, citations, attachments

Read the full file on GitHub · 181 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. 12d ago First seen · 181 lines · 63 tokens per session scan A 7bba543a6035

Subscribe to this mod's changes

trestle-oscal-models is a skill published in the GitHub repository oscal-compass-lab/compliance-trestle-skills (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 2,044 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

iso-27001

Use when the user asks about ISO/IEC 27001:2022 from an engineering perspective — building an ISMS that runs on systems and code rather than spreadsheets, instrumenting Annex A controls, designing risk registers as data, and producing evidence pipelines that hold up to a certification audit. Engineer-voice, not…

grcwarlock/compliance-as-code · 72 tokens

nist-800-53

Use when the user asks about NIST SP 800-53 Rev. 5 from an engineering perspective — selecting baselines, tailoring controls, modeling control inheritance from cloud providers and shared services, emitting OSCAL artifacts, or implementing controls in IaC and code rather than running them as a documentation exercise.…

grcwarlock/compliance-as-code · 76 tokens

soc-2

Use when the user asks about SOC 2 from an engineering perspective — Trust Services Criteria (TSC) implementation, evidence-as-code, continuous monitoring patterns, instrumenting controls, or designing systems that produce audit-ready evidence by default. Engineer-voice, not auditor-voice.

grcwarlock/compliance-as-code · 59 tokens

control-mapping

Maps NIST controls to FedRAMP requirements and documents. Use when helping with control implementation, compliance mapping, security baseline alignment, or understanding control requirements.

hackIDLE/fedramp-docs-mcp · 35 tokens

frmr-analysis

Analyzes FedRAMP FRMR documents to extract control mappings, KSI entries, and version changes. Use when the user asks about FedRAMP requirements, control mappings, compliance data, or needs to understand FRMR document content.

hackIDLE/fedramp-docs-mcp · 51 tokens

iso42001

Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance · 173 tokens