component-identification

component-identification is a skill for Claude Code, Codex from paruff/uFawkesAI. It costs 30 tokens per session (658 once invoked), scanned A, original, MIT.

A planning aid that maps a system design to the services, code modules, build and deployment pipelines, and GitOps files needed to build it.

In plain words
What is it for?
Use it to create a component map from an architecture and specification, including service ownership, module responsibilities, pipelines, deployment environments, and secret management.
Why use it?
It turns a high-level design into a concrete list of implementation parts, helping prevent missing components or unclear boundaries.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions Codex.

Good fit Use it to create a component map from an architecture and specification…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/paruff/ufawkesai/component-identification
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 paruff/uFawkesAI --skill component-identification
Clone the repo
git clone --depth 1 https://github.com/paruff/uFawkesAI

Made for: Claude Code, Codex.

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-identification

README.md
[![agentmods](https://agentmods.dev/badge/skills/paruff/ufawkesai/component-identification.svg)](https://agentmods.dev/skills/paruff/ufawkesai/component-identification)
Your own site
<a href="https://agentmods.dev/skills/paruff/ufawkesai/component-identification"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/component-identification.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 658 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.00030 $0.00658
Opus 5 $0.00015 $0.00329
Sonnet 5 $0.00006 $0.00132
Haiku 4.5 $0.00003 $0.00066

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

Security

Grade A, and why

component-identification 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.

.agents/skills/design/component-identification/SKILL.md · 110 lines

How it starts

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

Skill: Component Identification

Load trigger: "load component-identification skill" > DORA: Cap 3 (AI-Accessible Internal Data) Token cost: Low

Purpose

Identify the components required to implement the design.

Responsibilities

  • Identify services
  • Identify modules
  • Identify pipelines
  • Identify GitOps components

Inputs

  • architecture.json (from architecture-decomposition skill)
  • specification.md

Outputs

  • component-map.json

Identification Rules

Services

  • Each service has a clear ownership boundary
  • Services communicate through defined APIs
  • Services can be deployed independently
  • Services have distinct data stores (where applicable)

Modules

  • Each module has a single responsibility
  • Modules are reusable where possible
  • Module interfaces are well-defined
  • No circular module dependencies

Pipelines

  • Each service has a build pipeline
  • Shared pipelines for common tasks
  • Deployment pipelines per environment

GitOps Components

  • Base manifests defined
  • Environment overlays defined
  • Secret management approach defined

Component Types

Type Purpose Example
API Service Handle HTTP requests User API, Payment API
Worker Process async jobs Email Worker, Report Worker
CLI Tool Command-line interface Migration Tool, Admin CLI
Library Shared code Auth Library, Utils Library
Pipeline CI/CD automation Build Pipeline, Deploy Pipeline
Manifest K8s resources Deployment, Service, ConfigMap

Output Format

{
  "services": [
    {
      "name": "service-name",
      "type": "api | worker | cli | library",
      "language": "typescript | python | go",
      "port": 3000,
      "database": "postgresql",
      "dependencies": ["other-service"]
    }
  ],
  "pipelines": [
    {
      "name": "pipeline-name",
      "type": "build | deploy | security",
      "triggers": ["push", "pr"],
      "stages": ["lint", "test", "build", "deploy"]
    }
  ],
  "gitops": {
    "base": "base/",
    "overlays": ["dev", "staging", "production"],
    "secret_management": "external-secrets"  # pragma: allowlist secret
  }
}

Read the full file on GitHub · 110 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 · 110 lines · 30 tokens per session scan A 2ee0a3413557

Subscribe to this mod's changes

component-identification is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 14d ago), licensed MIT. It adds 30 tokens to every session and 658 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-31.

Related

Other skills, from other repositories

planning-with-files

Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…

mxyhi/ok-skills · 117 tokens

infrastructure-overview

Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…

docxology/template · 80 tokens

infrastructure-validation

Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.

docxology/template · 54 tokens

template-academic-paper

Template-native manuscript planning, outline, drafting, revision, formatting, citation check, and AI-use disclosure routing. USE WHEN the user asks to write, outline, revise, format, or prepare a paper inside the Research Project Template.

docxology/template · 52 tokens

infrastructure-llm

Skill for the LLM infrastructure module providing local Large Language Model integration via Ollama. Covers client initialization, prompt templates, output validation, manuscript review generation, conversation context, and CLI usage. Use when querying LLMs, generating manuscript reviews, validating LLM outputs, or…

docxology/template · 66 tokens

research-workflow

Seven-stage research workflow (SCOPE→LITERATURE→REASON→DESIGN→COMPUTE→SYNTHESIZE→WRITE). Use for: structuring an AI agent's research process, generating literature review prompts, scoping methodology. Usage: from infrastructure.research import ResearchWorkflow; ResearchWorkflow.describe() Config: set stage overrides…

docxology/template · 91 tokens