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 skills/oscal-compass-lab/compliance-trestle-skills/compliance-trestle-engineeringWrote 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/oscal-compass-lab/compliance-trestle-skills/compliance-trestle-engineering)<a href="https://agentmods.dev/skills/oscal-compass-lab/compliance-trestle-skills/compliance-trestle-engineering"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/compliance-trestle-engineering/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/oscal-compass-lab/compliance-trestle-skills/compliance-trestle-engineering"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/compliance-trestle-engineering.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.00043 | $0.00760 |
| Opus 5 | $0.00022 | $0.00380 |
| Sonnet 5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
compliance-trestle-engineering 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Trestle Engineering
Use this skill when an agent must operate a Compliance Trestle workspace. Use it to import or validate OSCAL models, assemble markdown, regenerate OSCAL, or turn legacy SSP content into a traceable Trestle-managed workflow.
Required guardrails
- Preserve source traceability for every generated OSCAL field that came from a legacy PDF, DOCX, Markdown, TXT file, interview note, spreadsheet, ticket, or evidence package.
- Never invent control mappings. If the source does not clearly support a mapping, set status to
needs_reviewand explain the uncertainty. - Schema-valid OSCAL is not a statement of compliance effectiveness.
- Keep reviewer-owned decisions in review queues or traceability maps.
- Do not hide reviewer decisions in generated prose.
- Prefer small, reversible Trestle operations.
- Do not do large opaque rewrites.
Standard workflow
- Start or inspect the workspace.
trestle inittrestle versionfind . -maxdepth 3 -type d | sort
- Import or create OSCAL artifacts.
- catalogs under
catalogs/ - profiles under
profiles/ - component definitions under
component-definitions/ - SSPs under
system-security-plans/
- catalogs under
- Resolve the applicable profile before you write control implementations.
- Author or update markdown with source references.
- Assemble markdown back into OSCAL.
- Validate with Compliance Trestle and any available OSCAL validator.
- Make review outputs for
needs_review, unmapped, or low-confidence items.
Typical commands
Use the wrapper when you want consistent reports:
bash scripts/trestle-workflow.sh init workspaces/acme/trestle-workspace
bash scripts/trestle-workflow.sh validate workspaces/acme/trestle-workspace
bash scripts/trestle-workflow.sh assemble workspaces/acme/trestle-workspace markdown/system-security-plans/acme-ssp acme-ssp
bash scripts/trestle-workflow.sh status workspaces/acme/trestle-workspace
Use raw Trestle when the reviewer needs exact CLI control:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 79 lines · 43 tokens per session scan A 8e98673f14f3
compliance-trestle-engineering 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 43 tokens to every session and 760 once invoked, about $0.0002 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 skills, from other repositories
executing-nist-rmf-authorization-to-operate
Drive a federal system through the NIST Risk Management Framework (SP 800-37 Rev 2) to an Authorization to Operate (ATO): Prepare, Categorize (FIPS 199), Select a control baseline (FIPS 200 / SP 800-53 Rev 5), Implement, Assess (SP 800-53A), Authorize, and Monitor continuously. Use when a system needs an ATO or a…
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…
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.…
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.
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.
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.