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 oscal-compass-lab/compliance-trestle-skills --skill trestle-compliance-pipelinegit clone --depth 1 https://github.com/oscal-compass-lab/compliance-trestle-skillsWrote 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/trestle-compliance-pipeline)<a href="https://agentmods.dev/skills/oscal-compass-lab/compliance-trestle-skills/trestle-compliance-pipeline"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/trestle-compliance-pipeline/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/trestle-compliance-pipeline"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/trestle-compliance-pipeline.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.00103 | $0.03092 |
| Opus 5 | $0.00051 | $0.01546 |
| Sonnet 5 | $0.00021 | $0.00618 |
| Haiku 4.5 | $0.00010 | $0.00309 |
Grade A, and why
trestle-compliance-pipeline 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End-to-End Compliance Pipeline
This skill describes the full compliance pipeline. The pipeline starts with regulation authoring. The pipeline ends with assessment results. Topics include persona ownership, multi-repository coordination, and the Compliance-to-Policy (C2P) bridge. The bridge connects OSCAL artifacts to runtime policy validation.
GRC Personas and Artifact Ownership
Each compliance artifact has a primary owner persona. Artifacts flow downstream to consumers:
| Persona | Primary Artifact | Key Trestle Commands | Downstream Consumer |
|---|---|---|---|
| Regulators | Catalog | catalog-generate, catalog-assemble |
Compliance Officers |
| Compliance Officers / CISO | Profile | profile-generate, profile-assemble, xlsx-to-oscal-profile |
Control Providers, System Owners |
| Control Providers (vendors) | Component Definition (Service) | csv-to-oscal-cd, component-generate, component-assemble |
Control Assessors, System Owners |
| Control Assessors (PVP vendors) | Component Definition (Validation) | csv-to-oscal-cd (with Check_Id column) |
CPAC / C2P |
| System Owners / CIO | System Security Plan | ssp-generate, ssp-assemble, ssp-filter |
Assessors, Auditors |
| Assessors | Assessment Results | xccdf-result-to-oscal-ar, tanium-result-to-oscal-ar |
CISO, System Owners |
| Operations | Remediation (POA&M) | create, split, merge (JSON workflow) |
Auditors |
Key principle: Each persona manages its artifact independently. Artifacts flow downstream through Git-based propagation. This supports separation of duties. This also supports independent versioning.
Per-Persona Authoring Workflows
Regulators: Catalog Authoring
Regulators publish security controls as catalogs. Examples: NIST 800-53, PCI-DSS, ISO 27001.
# Import existing catalog or create new one
trestle import -f nist-800-53-catalog.json -o nist-800-53
# Generate markdown for human editing
trestle author catalog-generate --name nist-800-53 --output md_catalogs/nist-800-53
# Edit control markdown files (one per control, grouped by family)
# Then reassemble
trestle author catalog-assemble --markdown md_catalogs/nist-800-53 --output nist-800-53
What ships with it
2 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 · 347 lines · 103 tokens per session scan A aabc5c42ee24
trestle-compliance-pipeline 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 103 tokens to every session and 3,092 once invoked, about $0.0005 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
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.
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…