component-definition

component-definition is a skill for Claude Code from oscal-compass/agentic-agile-authoring. It costs 57 tokens per session (1,108 once invoked), scanned A, original, Apache-2.0.

A tool for describing how a specific service, operating system, application, or checking tool meets the requirements in an OSCAL catalog or profile. OSCAL is NIST’s machine-readable format for security and compliance requirements.

In plain words
What is it for?
Use it to identify components, map their rules to OSCAL controls, author the mappings in CSV, and create a validated component-definition.json file. It can describe both components that enforce rules and tools that verify them.
Why use it?
A catalog states what a security control requires, but not how one particular component satisfies it. This turns those general requirements into concrete rules and checks that can be reviewed or tested.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to identify components, map their rules to OSCAL controls, author…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oscal-compass/agentic-agile-authoring/component-definition
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.

Any agent
npx skills add oscal-compass/agentic-agile-authoring --skill component-definition
Clone the repo
git clone --depth 1 https://github.com/oscal-compass/agentic-agile-authoring

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/oscal-compass/agentic-agile-authoring/component-definition.svg)](https://agentmods.dev/skills/oscal-compass/agentic-agile-authoring/component-definition)
Your own site
<a href="https://agentmods.dev/skills/oscal-compass/agentic-agile-authoring/component-definition"><img src="https://agentmods.dev/badge/skills/oscal-compass/agentic-agile-authoring/component-definition.svg" alt="Measured on agentmods" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,108 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.00057 $0.01108
Opus 5 $0.00028 $0.00554
Sonnet 5 $0.00011 $0.00222
Haiku 4.5 $0.00006 $0.00111

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

Security

Grade A, and why

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.

The scan reads SKILL.md. This mod also ships 1 executable file (csv_to_markdown.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/component-definition/SKILL.md · 107 lines

How it starts

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

Component Definition

Purpose

Given a component (a concrete system element such as a service, OS, or audit tool), translate the high-level abstract controls defined in an OSCAL catalog or profile into component-specific, actionable control implementations.

This skill bridges the gap between what a control requires in the abstract and how a specific component fulfills or checks it in practice.

Concepts

  • service component: implements controls directly (firewall, OS, middleware, application)
  • validation component: verifies that another component's rules are actually enforced (scanner, audit tool, monitoring agent)

A component definition captures rules per component, maps them to catalog controls, and optionally links validation checks to service rules.

Main Tasks

  1. Identify which components are in scope and their type (service / validation)
  2. Map catalog/profile controls to component-level rules
  3. Author CSV expressing those rules and mappings
  4. Generate component-definition.json from the CSV

Sub-skills

  • csv-authoring.mdSTART HERE — Detailed guide to authoring CSV files for component definitions using Python csv.writer()
  • csv-to-markdown.md — Generate human-readable markdown preview of component definition CSV before OSCAL conversion
  • csv-to-oscal-cd.md — Convert an authored CSV into an OSCAL component definition using the trestle_task_csv_to_oscal_cd MCP tool

Workflow

  1. Confirm the trestle workspace and target profile/catalog with the user
  2. Identify components and their types (ask user for validation component if not specified)
  3. For each component, enumerate the rules and map them to control IDs
  4. Author CSV using Python csv.writer() (see csv-authoring.md for detailed guidance)
    • Use Python lists, not manual string concatenation
    • Verify column counts and namespace URLs programmatically
    • Never use write_to_file for CSV construction
  5. Generate markdown preview using csv_to_markdown.py to show component vs control vs rule/check mappings
  6. Confirm CSV content with the user before generating
  7. Invoke trestle_task_csv_to_oscal_cd to produce component-definition.json

Read the full file on GitHub · 107 lines

Files

What ships with it

6 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.

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 · 107 lines · 57 tokens per session scan A 30cd27f3c2de

Subscribe to this mod's changes

component-definition is a skill published in the GitHub repository oscal-compass/agentic-agile-authoring (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,108 once invoked, about $0.0003 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens