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-authoring-workflowgit 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-authoring-workflow)<a href="https://agentmods.dev/skills/oscal-compass-lab/compliance-trestle-skills/trestle-authoring-workflow"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/trestle-authoring-workflow/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-authoring-workflow"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/trestle-authoring-workflow.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.00076 | $0.02694 |
| Opus 5 | $0.00038 | $0.01347 |
| Sonnet 5 | $0.00015 | $0.00539 |
| Haiku 4.5 | $0.00008 | $0.00269 |
Grade A, and why
trestle-authoring-workflow 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trestle Authoring Workflow
The Generate-Edit-Assemble Cycle
Trestle authoring tools convert OSCAL JSON to markdown for human editing. Then they convert markdown back to JSON:
JSON (OSCAL) → generate → Markdown (edit) → assemble → JSON (OSCAL)
This cycle continues. After the first generate, edit markdown and assemble again.
Author Commands by Model Type
Catalog Authoring
trestle author catalog-generate --name <catalog> --output <md_dir>→ markdown per controltrestle author catalog-assemble --markdown <md_dir> --output <catalog>→ JSON catalog
Profile Authoring
trestle author profile-generate --name <profile> --output <md_dir>→ markdown with profile additionstrestle author profile-assemble --markdown <md_dir> --output <profile>→ JSON profiletrestle author profile-resolve --name <profile> --output <resolved>→ resolved profile catalog
Component Definition Authoring
trestle author component-generate --name <compdef> --output <md_dir>→ markdown per component/controltrestle author component-assemble --markdown <md_dir> --output <compdef>→ JSON component-definition
SSP Authoring
trestle author ssp-generate --profile <profile> --compdefs <comp1,comp2> --output <md_dir>→ markdown per controltrestle author ssp-assemble --markdown <md_dir> --output <ssp>→ JSON SSPtrestle author ssp-filter --name <ssp> --profile <profile> --output <filtered>→ filtered SSP
Markdown Structure
Control Markdown File
Each control gets its own .md file with:
- YAML header: metadata, parameters, properties
- Control title:
# control-id - [Group Title] Control Title - Control Statement:
## Control Statementwith labeled parts - Control guidance:
## Control guidance - Additional sections: Implementation responses, component sections
YAML Header Tags (x-trestle-*)
| Tag | Purpose |
|---|---|
x-trestle-set-params |
Parameter values for the control |
x-trestle-global |
Global metadata (sort-id, profile title) |
x-trestle-sections |
Map of section short names to display names |
x-trestle-add-props |
Properties to add to the control |
x-trestle-comp-def-rules |
Rules from component definitions |
x-trestle-comp-def-rules-param-vals |
Rule parameter values |
x-trestle-inherited-props |
Properties inherited from upstream |
x-trestle-leveraging-comp |
Leveraged component information |
x-trestle-statement |
Statement-level metadata |
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 · 299 lines · 76 tokens per session scan A 607cfb4a19e8
trestle-authoring-workflow 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 76 tokens to every session and 2,694 once invoked, about $0.0004 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…