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.
npx skills add harness/harness-skills --skill create-sbomgit clone --depth 1 https://github.com/harness/harness-skillsWrote 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.
[](https://agentmods.dev/skills/harness/harness-skills/create-sbom)<a href="https://agentmods.dev/skills/harness/harness-skills/create-sbom"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/create-sbom/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/harness/harness-skills/create-sbom"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/create-sbom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 128 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00177 | $0.05997 |
| Opus 5 | $0.00088 | $0.02998 |
| Sonnet 5 | $0.00035 | $0.01199 |
| Haiku 4.5 | $0.00018 | $0.00600 |
Grade A, and why
create-sbom 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-sbom — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create SBOM
Add an SBOM Orchestration (SscaOrchestration) step to an existing Harness pipeline for a
container image or code repository. This skill only works with existing pipelines — do not
create standalone SBOM pipelines.
Supported stages: SBOM Orchestration runs in CI, CD (Deployment), and Security
(Security) stages. Show stage type in Phase 2 and offer placement options that match the stage
type (see references/interactive-wizard-flow.md).
Guide the user through a step-by-step interactive wizard (same UX as /configure-repo-scan):
one decision per turn, recommended options marked, pipeline structure
shown after fetch, then confirm before harness_update.
- Wizard scripts:
references/interactive-wizard-flow.md - UI ↔ YAML mapping:
references/sbom-orchestration-step.md - CD containerized step groups:
references/cd-containerized-step-group.md
Interaction model (mandatory)
Follow this UX for every invocation. Do not dump all Pipeline Studio fields in one message.
- One question per turn — use the
AskQuestiontool when available. If unavailable, use a numbered option list with(Recommended)on the default choice (same pattern as container scan). - Opening message — briefly state the goal: add SBOM Orchestration to an existing pipeline.
- Progress breadcrumb — after pipeline fetch, show on each wizard turn:
Pipeline · Placement · Method · Source · Details · Attestation · Submit - Record answers — keep a running summary of choices; do not re-ask unless the user changes direction.
- Fetch before configure —
harness_get(URL or id) before placement/source questions. - Show pipeline structure — list stages and steps (Phase 2) before asking placement.
- Infer, don’t assume — suggest connector/source from YAML; skip connector question if unambiguous.
- Never guess image tags — always ask for image or repo+branch in Phase 8.
- Confirm before write — Phase 10 summary +
harness_updateonly after user confirms. - Stop after update — after successful
harness_update, provide a configuration summary and point the user to/run-pipelineto execute. Do not callharness_execute, poll executions, or runharness_diagnosein this skill (same pattern as/configure-repo-scan). - “Defaults” shortcut — apply recommended wizard choices (see reference) but still ask for image/repo.
- Phase 3 Placement is never optional — always run Phase 2 (structure) then Phase 3
(
AskQuestionfor stage + position) before method/source/attestation, even when:- The pipeline has only one CI stage
- An
SscaOrchestrationstep already exists in CI - The user said “add SBOM to the pipeline” without naming a stage
- A prior chat configured the same pipeline (do not reuse that to skip Placement)
- Never assume pipeline or stage from session history — confirm pipeline URL/ID in Phase 0/1 unless the user pasted it in the current message. Prior workspace context may inform suggestions, not replace the wizard.
- CD is a different placement path — if the user chooses a
Deploymentstage (or asks for CD), followreferences/cd-containerized-step-group.mdend to end (step group,<+artifact.image>, infra). Do not place CD SBOM underexecution.stepsat the stage top level. - CI-only pipeline + CD SBOM — if Phase 2 shows no
Deploymentstage and the user wants CD, run the CD prerequisites sub-flow (service, environment, infrastructure, K8s connector forstepGroupInfra) beforeharness_update. See CD edge case below.
What ships with it
3 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.
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.
- 9d ago First seen · 602 lines · 177 tokens per session scan A 093deaa4f21c
create-sbom is a skill published in the GitHub repository harness/harness-skills (105 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 177 tokens to every session and 5,997 once invoked, about $0.0009 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-30.
Other skills, from other repositories
secrets-management
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.