oscal-component-definition

oscal-component-definition is a skill for Claude Code from metaschema-framework/claude-plugins. It costs 25 tokens per session (1,770 once invoked), scanned A, original, CC0-1.0.

A reusable description of how a product, service, policy, or process satisfies security controls. OSCAL is a standard format for exchanging cybersecurity and compliance information.

In plain words
What is it for?
Use it to document the security behavior of software, hardware, cloud services, policies, procedures, and other reusable components.
Why use it?
It prevents teams from rewriting the same control-implementation details for every system security plan.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the oscal plugin — 9 skills shipped together

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.

agentmods
npx agentmods add skills/metaschema-framework/claude-plugins/oscal-component-definition
Any agent
npx skills add metaschema-framework/claude-plugins --skill oscal-component-definition
Clone the repo
git clone --depth 1 https://github.com/metaschema-framework/claude-plugins

Made for: Claude Code.

Or install oscal, the plugin that ships this one along with the rest of its 9 skills.

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 oscal-component-definition

README.md
[![agentmods](https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/oscal-component-definition.svg)](https://agentmods.dev/skills/metaschema-framework/claude-plugins/oscal-component-definition)
Your own site
<a href="https://agentmods.dev/skills/metaschema-framework/claude-plugins/oscal-component-definition"><img src="https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/oscal-component-definition.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,770 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00025 $0.01770
Opus 5 $0.00013 $0.00885
Sonnet 5 $0.00005 $0.00354
Haiku 4.5 $0.00003 $0.00177

Measured 6d ago against content hash 445a925522ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

oscal-component-definition 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 6d 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.

plugins/oscal/skills/oscal-component-definition/SKILL.md · 271 lines

How it starts

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

OSCAL Component Definition Model

The Component Definition model describes how components (hardware, software, services, policies, processes) can satisfy security controls. Component definitions are reusable across multiple systems.

Related skills:

  • oscal-ssp - System Security Plans that incorporate components
  • oscal-profile - Baselines that define required controls

Purpose

Component definitions:

  • Document control implementations for products/services
  • Enable reuse across multiple system security plans
  • Support supply chain security documentation
  • Describe configuration options for security compliance

Component Types

Type Examples
software Operating systems, applications, databases
hardware Servers, network devices, HSMs
service Cloud services, managed services
policy Security policies, procedures
process Operational processes, workflows
procedure Step-by-step instructions
plan Contingency plans, incident response
guidance Security guidance documents
standard Technical standards
validation FIPS 140-2 certificates, FedRAMP ATOs

Document Structure

component-definition:
  uuid: <unique-identifier>
  metadata:
    title: "Component Name"
    version: "1.0.0"
    oscal-version: "1.1.2"
  import-component-definitions: []  # Reference other components
  components:
    - uuid: component-uuid
      type: software
      title: "Product Name"
      description: "Product description"
      control-implementations: []
  capabilities: []                  # Optional capability groupings
  back-matter:
    resources: []

Components

Basic Component Definition

components:
  - uuid: "550e8400-e29b-41d4-a716-446655440000"
    type: software
    title: "Enterprise Database Server"
    description: "Relational database management system"
    props:
      - name: vendor
        value: "Database Corp"
      - name: version
        value: "15.2"
    protocols:
      - uuid: protocol-uuid
        name: https
        port-ranges:
          - start: 443
            end: 443
            transport: TCP
    control-implementations:
      - uuid: impl-uuid
        source: "profile.json"
        description: "Controls implemented by this component"
        implemented-requirements: []

Read the full file on GitHub · 271 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. 6d ago First seen · 271 lines · 25 tokens per session scan A 445a925522ec

Subscribe to this mod's changes

oscal-component-definition is a skill published in the GitHub repository metaschema-framework/claude-plugins (10 stars, last pushed 6mo ago), licensed CC0-1.0. It adds 25 tokens to every session and 1,770 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

specification-writing

Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens