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/review-oscal-mappingsWrote 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/review-oscal-mappings)<a href="https://agentmods.dev/skills/oscal-compass-lab/compliance-trestle-skills/review-oscal-mappings"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/review-oscal-mappings/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/review-oscal-mappings"><img src="https://agentmods.dev/badge/skills/oscal-compass-lab/compliance-trestle-skills/review-oscal-mappings.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.00035 | $0.00385 |
| Opus 5 | $0.00017 | $0.00192 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
review-oscal-mappings 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.
What it actually says
Review OSCAL Mappings
Human-in-the-loop review workflow for source traceability and mapping quality.
Read first
docs/OSCAL-REVIEW-WORKFLOW.mdadapters/generic-agent-package/prompts/review-oscal-mappings.mdplugins/document-transform/oscal-document-workbench/templates/review-queue.mdplugins/document-transform/oscal-document-workbench/templates/control-mapping-review.csv
Steps
- Load
source-map.csvand any generatedreports/review-queue.md. - For each
needs_reviewor unmapped row:- make sure the source text supports the OSCAL target
- mark unsupported claims
needs_revieworreject - identify missing evidence
- keep reviewer notes
- Make or update the review queue:
bash plugins/document-transform/oscal-document-workbench/scripts/build-review-queue.sh <workspace>/extracted/source-map.csv --output <workspace>/reports/review-queue.md
- Summarize counts of mapped,
needs_review, and unmapped items. - Block "ready for assessment" claims while unresolved review rows remain.
Reviewer decisions
Use explicit statuses in the traceability map.
Allowed source-map.csv statuses:
mappedneeds_reviewunmappedreject
Allowed reviewer decisions in the queue. Keep these separate from mapping status:
approveremaprejectneeds_more_evidencedefer
Do not silently rewrite uncertain source statements as implemented technical reality.
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 · 55 lines · 35 tokens per session scan A 0e48c3fe5c14
review-oscal-mappings 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 35 tokens to every session and 385 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
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…