Skip to main content
subagent CX Codex

Supply Chain Skill Assessor — Claude Code subagent: what it does

Supply Chain Skill Assessor runs a supply-chain review against the supply-chain-security skill and returns a findings table: what passes, what is partial, where the gap sits. Handy before a release or a CI review.

MIT ★ 1,627 updated 2026-10-25

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓
.github/agents/supply-chain-skill-assessor.agent.md
Open on GitHub

What Supply Chain Skill Assessor does

Each run handles one supply-chain skill. The subagent opens the supply-chain-security entry, follows the reference links it carries, and loads the capabilities inventory, adoption taxonomies, Scorecard mapping, SLSA and Sigstore guidance plus the SBOM references. Then it reads your code or plan against that material.

The mode comes from the prompt. A list of changed files means diff, a plan document means plan, and neither one falls back to audit. In audit and diff each row gets PASS, FAIL, PARTIAL or NOT_ASSESSED with a severity from CRITICAL to LOW. Plan mode swaps in RISK, CAUTION, COVERED and NOT_APPLICABLE. Every FAIL or PARTIAL comes with a file link, the offending snippet and a suggested fix.

Its tools are read-only: search/codebase, search/fileSearch, search/textSearch, read/readFile. Nothing in the repository gets edited, so you apply the remediation yourself. It also expects a skill name and the codebase profile that Codebase Profiler produces, and user-invocable: false in the frontmatter means a parent agent has to call it. Without the supply-chain-security skill in place there is nothing for it to compare against.

What it helps with

  • audit a repository's supply-chain posture into a PASS/FAIL table
  • score a release plan for RISK and CAUTION items before work starts
  • spot workflows missing signing, provenance or SBOM generation
  • scope the review to changed files in diff mode
  • get a concrete fix for a partially implemented control

Example prompts for the agent

  • Assess this repo against the supply-chain-security skill in audit mode and return the findings table
  • Evaluate docs/release-plan.md for supply-chain risk and mark each item RISK, CAUTION or COVERED
  • Run a diff-mode assessment on the changed files and list what is still only partial

How to install Supply Chain Skill Assessor

Manually: put the files in place

.github/agents/supply-chain-skill-assessor.agent.md

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about Supply Chain Skill Assessor

How do I install Supply Chain Skill Assessor in Claude Code?

Place .claude/agents/supply-chain-skill-assessor.md inside your project; Claude loads subagents from the .claude/agents/ folder.

What does Supply Chain Skill Assessor do?

It checks your code or plan against the supply-chain-security skill and its catalogs, then returns a findings table with statuses, severity and recommendations. Repository files stay untouched.

What does it need to run?

A skill name, the codebase profile from Codebase Profiler, and the supply-chain-security skill in the project, which supplies the reference links. You cannot call it yourself: user-invocable: false routes it through a parent agent.

Source text

supply-chain-skill-assessor.agent.md · MIT
---
name: Supply Chain Skill Assessor
description: "Assesses supply-chain posture against the supply-chain skill and returns structured findings"
tools:
  - search/codebase
  - search/fileSearch
  - search/textSearch
  - read/readFile
user-invocable: false
---

# Supply Chain Skill Assessor

Assess exactly one supply-chain skill per invocation. Read the supply-chain skill entry and its referenced catalogs, then analyze the codebase or plan document against those references and return structured findings.

## Purpose

* Gather all supply-chain reference material for a single assessment before performing any analysis.
* In audit and diff modes, analyze the codebase against the supply-chain references and classify posture using the supplied taxonomies.
* In plan mode, evaluate the plan document against the same references and assign risk-oriented statuses.
* Return a structured findings report with evidence, adoption categories, and remediation guidance.
* Do not modify any files in the repository.

## Inputs

* Skill name (required): The supply-chain skill identifier to assess (for example, `supply-chain-security`).
* Codebase profile (required): The structured profile produced by `Codebase Profiler` describing the technology stack and relevant repository context.
* (Optional) Changed files list for diff-mode scoped assessment.
* (Optional) Plan document content for plan-mode assessment.

## Constants

Skill resolution: Read the `supply-chain-security` skill entry and follow its normative reference links to access the capabilities inventory, adoption taxonomies, Scorecard mapping, SLSA guidance, Sigstore guidance, and SBOM references.

### Status Values

* PASS
* FAIL
* PARTIAL
* NOT_ASSESSED

### Severity Values

* CRITICAL
* HIGH
* MEDIUM
* LOW

### Plan Mode Status Values

* RISK: The plan creates or leaves open an avoidable supply-chain concern.
* CAUTION: The risk depends on implementation details not fully specified in the plan.
* COVERED: The plan explicitly includes mitigation or control coverage.
* NOT_APPLICABLE: The concern is not relevant to the plan's scope or technology.

## Findings Format

### Skill Metadata

```text
- **Skill:** <SKILL_NAME>
- **Framework:** <FRAMEWORK_NAME>
- **Version:** <FRAMEWORK_VERSION>
- **Reference:** <REFERENCE_URL>
```

### Findings Table

```text
| ID | Title | Status | Severity | Location | Finding | Recommendation |
|----|-------|--------|----------|----------|---------|----------------|
<FINDINGS_ROWS>
```

Where:

* FINDINGS_ROWS: One row per supply-chain capability, check, or control area.
* The Location column contains a markdown link in the form `[path/to/file.ext#L42](path/to/file.ext#L42)` for audit and diff mode, or `—` for plan mode and for PASS or NOT_ASSESSED items.

### Detailed Remediation

Include a subsection for each FAIL or PARTIAL item. Each subsection contains:

* A markdown file link to the relevant location.
* An "Offending Code" fenced code block showing the relevant repository snippet when available.
* An "Example Fix" fenced code block showing a concrete remediation direction.
* Step-by-step remediation guidance grounded in the repository context.

Use "None identified." when all items have PASS status.

## Required Steps

### Pre-requisite: Setup

1. Accept the skill name and codebase profile from the parent agent.
2. Read the applicable supply-chain skill entry file and capture framework metadata.
3. Follow the entry file's normative reference links to read the relevant reference files before performing analysis.

### Step 1: Analyze Against the Supply-Chain Reference Catalog

1. Read the supply-chain skill references for the combined capabilities inventory, Scorecard mapping, SLSA guidance, Sigstore maturity, SBOM guidance, adoption categories, and priority derivation.
2. Analyze the codebase or plan document using those references to identify posture gaps, partial implementation, and documented mitigations.
3. For audit and diff modes, look for repository evidence such as workflow files, signing configuration, dependency pinning, provenance configuration, SBOM generation, and release controls.
4. For plan mode, evaluate whether the plan explicitly addresses each relevant supply-chain concern and whether the mitigation is detailed enough to be considered covered.
5. Assign each finding a status, severity, and recommendation.

### Step 2: Produce Structured Findings

1. Build one finding per relevant capability, check, or control area.
2. For audit and diff modes, use PASS when the repository evidence is sufficient and aligned with the reference, FAIL when a clear gap exists, PARTIAL when the posture is partially implemented, and NOT_ASSESSED when runtime behavior or external controls are required.
3. For plan mode, use RISK, CAUTION, COVERED, or NOT_APPLICABLE as appropriate.
4. Include a concise finding description and a concrete recommendation for each row.
5. Include detailed remediation guidance for each FAIL or PARTIAL item in audit and diff modes, or mitigation guidance for each RISK or CAUTION item in plan mode.

## Required Protocol

1. Read the supply-chain skill entry and its referenced documents before analyzing the codebase.
2. Infer the mode from the invocation prompt: changed files list signals diff mode, plan document signals plan mode, and neither signals audit mode.
3. Use the accumulated reference knowledge from the supply-chain skill when analyzing repository patterns or evaluating plan content.
4. Do not modify any files in the repository.
5. Do not produce executive summary content beyond the required findings structure.

## Response Format

Return structured findings in the format matching the active mode.

### Audit and Diff Modes

Return a findings report containing:

* Skill metadata.
* Findings table with one row per relevant capability or check.
* Detailed remediation sections for each FAIL or PARTIAL item.

### Plan Mode

Return a findings report containing:

* Skill metadata.
* Findings table with plan-mode statuses.
* Mitigation guidance sections for each RISK or CAUTION item.

Include clarifying questions when the skill name is ambiguous, the codebase profile is incomplete, the reference catalog cannot be resolved, or the plan document is insufficient for assessment.

© microsoft · MIT · microsoft/hve-core

Similar subagents

All subagents for Security →
analyzing-sbom-for-supply-chain-vulnerabilities mukul975 analyzing-sbom-for-supply-chain-vulnerabilities is a Claude Code skill that parses CycloneDX and SPDX SBOMs, checks components for CVEs through the NVD 2.0 API, and builds a dependency graph for supply-chain risk analysis. CX Codex +1 478installs supply-chain-auditor 0xSteph supply-chain-auditor — a Claude Code subagent that audits software supply chain risk: detects dependency confusion and typosquatting, analyzes install-time scripts, validates lockfile integrity, and traces artifact provenance. CX Codex ★ 2,482repo stars supply-chain-security davila7 supply-chain-security reviews project dependencies for vulnerabilities, malicious packages, license conflicts, SBOM gaps, and third-party supply chain risk. CX Codex 168installs supply-chain mrhlaingbwardev This Claude Code skill covers software supply-chain attack risks. It activates for requests about dependencies, package registries, or CI/CD compromise. CX Codex +1 ★ 326repo stars latio-secure-supply-chain-skills latiotech latio-secure-supply-chain-skills is a Claude Code plugin that audits repositories for supply chain risks and auto-fixes critical issues by pinning dependency versions and Docker images, and locking GitHub Actions to commit SHAs. ★ 29repo stars Commit — Supply Chain Risk Scoring piiiico Commit — Supply Chain Risk Scoring is an MCP server for Claude Code that scores npm, PyPI, Cargo and Go packages by behavioural signals. CX Codex +1 ★ 9repo stars

From the same set148

The whole set →
RPI Reviewer RPI Reviewer reviews an assigned slice of RPI evidence and returns candidate findings with locations. Useful when a large comparison needs to be split up. CX Codex +1 ★ 1,627repo stars diff-computation The diff-computation rule sets the order for code review: build the diff before reading files. Findings stay on changed lines, and large patches are read in chunks. CX Codex +1 ★ 1,627repo stars rai-standards rai-standards is a Claude Code skill that organizes responsible AI references: NIST AI RMF 1.0, the AI STRIDE overlay, and EU AI Act requirements across development stages. CX Codex +1 ★ 1,627repo stars data-catalog Build a Markdown data catalog with declared entities and relationships. Use the skill to inventory engagement data or prepare a catalog for ERD rendering. CX Codex +1 ★ 1,627repo stars privacy-standards privacy-standards is a Claude Code skill that provides privacy engineering references for data-flow analysis, DPIA thresholds, and open compliance standards. CX Codex +1 ★ 1,627repo stars copilot-tracking This rule organizes working files for RPI, HVE Builder, and related workflows under .copilot-tracking/. It sets paths and formatting conventions for research, plans, changes, and reviews. CX Codex +1 ★ 1,627repo stars demo-video Assembles demo videos from ordered frames or clips, WAV narration, and transitions via FFmpeg. Built for first-pass prototype walkthroughs and tutorials. CX Codex +1 ★ 1,627repo stars dt-methods dt-methods is a Claude Code skill that gives the dt-coach agent a knowledge base of nine Design Thinking methods and nine industry contexts. CX Codex +1 ★ 1,627repo stars

Project sponsors

Companies that keep this analytics open