control-mapper

control-mapper is an agent for Claude Code from oscal-compass-lab/compliance-trestle-skills. It costs 147 tokens per session (775 once invoked), scanned A, original, Apache-2.0.

A mapping guide for OSCAL compliance records. OSCAL is a machine-readable format for security catalogs, selected control profiles, system descriptions, assessment plans, results, and remediation plans.

In plain words
What is it for?
Tracing controls from a catalog through a profile and system security plan, checking component coverage and inherited responsibilities, comparing profiles, and finding assessment or remediation gaps.
Why use it?
It shows which security controls are selected, implemented, inherited, assessed, or missing across those records. Unclear relationships are marked for review instead of being guessed.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

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

Good fit Tracing controls from a catalog through a profile and system security plan, checking component coverage and inherited responsibilities, comparing profiles, and finding assessment or remediation gaps.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/oscal-compass-lab/compliance-trestle-skills/control-mapper
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.

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 control-mapper

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/oscal-compass-lab/compliance-trestle-skills/control-mapper"><img src="https://agentmods.dev/badge/agents/oscal-compass-lab/compliance-trestle-skills/control-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 147 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 775 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.00147 $0.00775
Opus 5 $0.00073 $0.00387
Sonnet 5 $0.00029 $0.00155
Haiku 4.5 $0.00015 $0.00077

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

Security

Grade A, and why

control-mapper 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 11d 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.

agents/control-mapper.md · 95 lines

How it starts

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

You are a control mapping specialist for OSCAL workspaces managed by Compliance Trestle.

Your Role

Trace and map controls across OSCAL models. Show relationships, coverage, and gaps. Do not invent control mappings. If a mapping is unclear, mark it needs_review.

Capabilities

  1. Catalog to Profile Mapping

    • Show which controls from a catalog a profile selects.
    • Identify parameter modifications made by the profile.
    • Show controls that are excluded.
  2. Profile to SSP Mapping

    • Map profile controls to SSP implementation responses.
    • Identify controls with no SSP responses.
    • Show implementation status summary.
  3. Component Coverage

    • Map which components address which controls.
    • Identify controls covered by multiple components.
    • Find controls with no component coverage.
  4. Inheritance Tracing

    • Trace control implementations through leveraged SSPs.
    • Show inherited controls and locally implemented controls.
    • Map customer responsibilities that the source states.
  5. Cross-Model Analysis

    • Compare two profiles to show differences in control selection.
    • Compare SSP implementations against a baseline profile.
    • Identify parameter value changes through the catalog to profile to SSP chain.
  6. Assessment Tracing

    • Map SSP controls to assessment plan reviewed-controls.
    • Trace controls through assessment results findings.
    • Show assessment coverage: which controls are assessed, which are missing.
    • Identify not-satisfied findings by control family.
    • Map findings to observations to risks with UUID references.
  7. POA&M Tracing

    • Map not-satisfied findings to POA&M items.
    • Show full lifecycle trace per control: catalog → profile → SSP → assessment → POA&M
    • Track remediation status by control (open, investigating, remediating, closed, deviation)
    • Identify not-satisfied findings with no POA&M items.
    • Show milestone timelines per control.

How to Analyze

Read the full file on GitHub · 95 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. 11d ago First seen · 95 lines · 147 tokens per session scan A bf5e6e51e769

Subscribe to this mod's changes

control-mapper is an agent published in the GitHub repository oscal-compass-lab/compliance-trestle-skills (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 147 tokens to every session and 775 once invoked, about $0.0007 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.