Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
Signs and verifies CycloneDX BOMs using cdxgen's native JSON Signature Format (JSF) implementation via cdx-sign and cdx-verify, supporting granular component, service, and annotation signatures…
$ npx skills add cdxgen/cdxgen --skill bom-signing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cdxgen/cdxgen bom-signing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cdxgen/cdxgen.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-plugin/skills/bom-signing .claude/skills/bom-signing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bom-signing" agent skill from https://github.com/cdxgen/cdxgen/tree/master/claude-plugin/skills/bom-signing into .claude/skills/bom-signing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bom-signing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cdxgen/cdxgen/tree/master/claude-plugin/skills/bom-signingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cdxgen/cdxgen --skill bom-signing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cdxgen/cdxgen bom-signing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdxgen/cdxgen.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-plugin/skills/bom-signing .agents/skills/bom-signing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bom-signing" agent skill from https://github.com/cdxgen/cdxgen/tree/master/claude-plugin/skills/bom-signing into .agents/skills/bom-signing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bom-signing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cdxgen/cdxgen --skill bom-signing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cdxgen/cdxgen bom-signing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdxgen/cdxgen.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-plugin/skills/bom-signing .cursor/skills/bom-signing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bom-signing" agent skill from https://github.com/cdxgen/cdxgen/tree/master/claude-plugin/skills/bom-signing into .cursor/skills/bom-signing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bom-signing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cdxgen/cdxgen.git --path claude-plugin/skills/bom-signing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cdxgen/cdxgen --skill bom-signing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cdxgen/cdxgen bom-signing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdxgen/cdxgen.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-plugin/skills/bom-signing .gemini/skills/bom-signing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bom-signing" agent skill from https://github.com/cdxgen/cdxgen/tree/master/claude-plugin/skills/bom-signing into .gemini/skills/bom-signing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bom-signing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cdxgen/cdxgen bom-signingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cdxgen/cdxgen --skill bom-signing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cdxgen/cdxgen.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-plugin/skills/bom-signing .github/skills/bom-signing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bom-signing" agent skill from https://github.com/cdxgen/cdxgen/tree/master/claude-plugin/skills/bom-signing into .github/skills/bom-signing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bom-signing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cdxgen/cdxgen --skill bom-signing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cdxgen/cdxgen bom-signing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdxgen/cdxgen.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-plugin/skills/bom-signing .opencode/skills/bom-signing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bom-signing" agent skill from https://github.com/cdxgen/cdxgen/tree/master/claude-plugin/skills/bom-signing into .opencode/skills/bom-signing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bom-signing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
bom-signingSigns and verifies CycloneDX BOMs using cdxgen's native JSON Signature Format (JSF) implementation via cdx-sign and cdx-verify, supporting granular component, service, and annotation signatures…
Bom Signing is an agent skill from cdxgen/cdxgen. Signs and verifies CycloneDX BOMs using cdxgen's native JSON Signature Format (JSF) implementation via cdx-sign and cdx-verify, supporting granular component, service, and annotation signatures, parallel multi-signatures, and sequential signature chains. Use when asked to sign an SBOM, verify a BOM signature, establish BOM authenticity or non-repudiation, build an approval trail across pipeline stages, or generate signing keys.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Supply chain security. The repository describes itself as: Creates CycloneDX Bill of Materials (BOM) for your projects from source and container images. Supports many languages and package managers. Integrate in your CI/CD pipeline with…. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit e256966. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
cdxgen.github.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Bom Signing loads about 1.5k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 478 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from cdxgen/cdxgen at commit e256966, republished under its Apache-2.0 licence (© cdxgen). 478 words, ~1,516 tokens.
.claude/skills/bom-signing/SKILL.md (or your agent's skills folder).cdxgen ships a native JSON Signature Format (JSF) implementation that goes
beyond a single document-level signature. It supports granular signatures over
individual components, services, and annotations; parallel multi-signatures via
signers; and sequential signature chains via chain.
Read reference/safety.md first.
Never generate, read, paste, or transcribe private key material yourself, and never enter a passphrase on the user's behalf. Run the signing commands with paths the user provides, and if a key does not exist yet, give the user the command to create it and let them run it.
For a throwaway demo or test BOM, cdxgen can generate a keypair and sign in one step:
cdxgen -o /absolute/path/to/bom.json --generate-key-and-sign /absolute/path/to/projectThis is appropriate for testing signing workflows. It is not appropriate for release signing, where the key should come from the user's key management.
# Replace or create the root signature in place
cdx-sign -i /absolute/path/to/bom.json -k /absolute/path/to/builder_private.pem
# Write a signed copy to a new file, with an explicit algorithm
cdx-sign -i /absolute/path/to/bom.json -o /absolute/path/to/bom.signed.json \
-k /absolute/path/to/builder_private.pem -a RS512| Flag | Purpose |
|---|---|
-i, --input | BOM to sign |
-o, --output | Signed copy; omit to sign in place |
-k, --private-key | Private key, PEM format |
-a, --algorithm | JSF algorithm; default RS512. Also ES256, Ed25519 |
-m, --mode | replace (default), signers, chain |
--key-id | Key identifier recorded in the signature |
--sign-components | Sign individual components |
--sign-services | Sign individual services |
--sign-annotations | Sign annotations |
--attach | Attach the signature rather than replacing |
Defaults can come from SBOM_SIGN_ALGORITHM and SBOM_SIGN_MODE.
| Mode | Semantics | Use for |
|---|---|---|
replace | Replaces or creates the root signature | Build-time signing by the producer |
signers | Appends a parallel signature without replacing existing ones | Independent approvals from different teams |
chain | Appends to a sequential signature history | An ordered approval trail through pipeline stages |
Append a security review signature without destroying the builder's:
cdx-sign -i /absolute/path/to/bom.json -k /absolute/path/to/auditor_private.pem \
--mode signers --no-sign-components --no-sign-services --no-sign-annotationsNote the --no- prefixes: the reviewer signs the document, not every component,
which keeps the second signature cheap and its scope clear.
Build a chained history:
cdx-sign -i /absolute/path/to/bom.json -k /absolute/path/to/approver_private.pem --mode chainUse signers when approvals are independent and order does not matter. Use
chain when the order is itself the evidence.
cdx-verify -i /absolute/path/to/bom.json --public-key /absolute/path/to/public.pem
cdx-verify -i /absolute/path/to/bom.json --public-key /absolute/path/to/public.pem --deep--deep verifies granular component, service, and annotation signatures rather
than only the document signature. Use it whenever the BOM was signed with
--sign-components or --sign-services — a passing shallow check on such a BOM
does not establish that the component signatures are intact.
--platform targets platform-specific verification behaviour.
cdx-validate folds signature verification into full validation (JSON input
only):
cdx-validate -i /absolute/path/to/bom.json \
--public-key /absolute/path/to/public.pem --require-signature--require-signature makes an unsigned BOM a validation failure rather than a
silent pass. Prefer this in release gates. See bom-convert-validate.
Be precise about what a result does and does not establish:
--deep.© cdxgen, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in claude-plugin/skills/bom-signing of cdxgen/cdxgen.
Open the folder on GitHubat commit e256966
Bom Signing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bom Signing this skillcdxgen/cdxgen | 1.1k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Skill Scannergetsentry/skills | 1k | 4 repos | ~2.5k | Automated safety check: Warn | Apache-2.0 | |
| Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit | 481 | 1 repos | ~3.3k | Automated safety check: Pass | None | |
| Eu CraSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 943 | 1 repos | ~4k | Automated safety check: Pass | MIT | |
| Kesekit Checkcdppcorp/KESE-KIT | 361 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Packslipjdx/packslip | 136 | — | ~2.9k | Automated safety check: Pass | MIT |
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the…
cdppcorp/KESE-KIT
Run a pre-deployment security compliance checklist based on KISA guidelines.
jdx/packslip
Configure signed release manifests with packslip: add the jdx/packslip action or packslip create to a release workflow, declare completions, man pages, CLI specs, skills, and SBOMs as resources, and…
relizaio/rearm
Author CycloneDX-VEX or OpenVEX documents that import cleanly into ReARM.
cdxgen/cdxgen
Generates AI-BOM, MCP inventory, AI skill inventory, and AI authorship provenance documents with cdxgen, cataloging models, inference services, Hugging Face purls, MCP servers and their…
cdxgen/cdxgen
Runs supply-chain risk analysis on CycloneDX BOMs with cdx-audit predictive auditing and cdxgen --bom-audit embedded rules, covering npm and PyPI package compromise posture, CI permission risk…
cdxgen/cdxgen
Enriches an existing CycloneDX BOM with occurrence, callstack, reachability, data-flow, and crypto-flow evidence using cdxgen evinse, including Go analysis via Golem and Rust analysis via Rusi, and…
cdxgen/cdxgen
Explores and triages a CycloneDX BOM interactively with the cdxi REPL, using built-in commands for dependency trees, licenses, services, cryptographic assets, audit findings, evidence occurrences…
cdxgen/cdxgen
Converts CycloneDX BOMs to SPDX 3.0.1 JSON-LD or between CycloneDX spec versions with cdx-convert, and validates BOMs against JSON schema, deep consistency checks, and OWASP SCVS and EU Cyber…
cdxgen/cdxgen
Reviews a codebase's direct dependencies and designs lightweight, low-risk, zero-dependency custom replacements using cdxgen SBOM evidence, occurrence/callstack usage data, and license and…
Categories
Signs and verifies CycloneDX BOMs using cdxgen's native JSON Signature Format (JSF) implementation via cdx-sign and cdx-verify, supporting granular component, service, and annotation signatures…. Bom Signing is an agent skill from cdxgen/cdxgen. Signs and verifies CycloneDX BOMs using cdxgen's native JSON Signature Format (JSF) implementation via cdx-sign and cdx-verify, supporting granular component, service, and annotation signatures, parallel multi-signatures, and sequential signature chains.
Bom Signing fits situations like: asked to sign an SBOM; verify a BOM signature; establish BOM authenticity; non-repudiation.
Run `npx skills add cdxgen/cdxgen --skill bom-signing -a claude-code`. Or copy the skill folder (claude-plugin/skills/bom-signing in cdxgen/cdxgen) into .claude/skills/bom-signing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cdxgen/cdxgen --skill bom-signing -a codex`. Or copy the skill folder (claude-plugin/skills/bom-signing in cdxgen/cdxgen) into .agents/skills/bom-signing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cdxgen/cdxgen --skill bom-signing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bom-signing, .gemini/skills/bom-signing, .github/skills/bom-signing and .opencode/skills/bom-signing in your project.
SKILL.md names no scripts, command-line tools or credentials: Bom Signing is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: cdxgen.github.io. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Bom Signing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Bom Signing: Skill Scanner (getsentry/skills, 1k stars), Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 481 stars), Eu Cra (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 943 stars) and Kesekit Check (cdppcorp/KESE-KIT, 361 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cdxgen (a GitHub organization) maintains it in cdxgen/cdxgen, which has 1,085 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.
Source: cdxgen/cdxgen on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.