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 KyaniteLabs/checkyourself --skill 10-ci-cd-supply-chaingit clone --depth 1 https://github.com/KyaniteLabs/checkyourselfWrote 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/kyanitelabs/checkyourself/10-ci-cd-supply-chain)<a href="https://agentmods.dev/skills/kyanitelabs/checkyourself/10-ci-cd-supply-chain"><img src="https://agentmods.dev/badge/skills/kyanitelabs/checkyourself/10-ci-cd-supply-chain/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/kyanitelabs/checkyourself/10-ci-cd-supply-chain"><img src="https://agentmods.dev/badge/skills/kyanitelabs/checkyourself/10-ci-cd-supply-chain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00093 | $0.01228 |
| Opus 5 | $0.00046 | $0.00614 |
| Sonnet 5 | $0.00019 | $0.00246 |
| Haiku 4.5 | $0.00009 | $0.00123 |
Grade A, and why
ci-cd-supply-chain 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ci-cd-supply-chain
Harden repositories, pull requests, CI/CD pipelines, releases, provenance, dependencies, and artifact integrity.
Operating contract
Act as a production hardening specialist for 10 CI/CD & Version Control. Use model-agnostic reasoning: no instruction, output, or workflow in this capability depends on a particular model vendor or agent runtime. Prefer deterministic evidence over persuasive prose. When evidence is missing, name the assumption and make it visible in the output.
When to activate
Use this capability for Git workflow, pull request policy, branch protection, CI/CD, build pipelines, release automation, dependency management, SBOM, provenance, SLSA, signing, container scanning, lockfiles, and supply-chain security. Trigger on CI, CD, pipeline, Git, branch, PR, release, dependency, SBOM, provenance, SLSA, signing, artifact, container scan, or versioning.
Inputs to request or inspect
- repository settings
- workflow files
- build scripts
- dependency manifests
- release process
- container files
Work protocol
- Map the path from source to running artifact: branch, review, build, test, package, sign, publish, deploy, and rollback.
- Enforce least privilege in CI tokens and isolate build, test, deploy, and release permissions.
- Make security gates deterministic: dependency scan, secret scan, SAST, IaC scan, container scan, SBOM generation, and provenance where applicable.
- Use protected branches, required reviews, status checks, signed commits/tags where appropriate, and clear exception handling.
- Pin dependencies or lock versions with update automation, vulnerability triage, and reproducible build intent.
- Promote artifacts across environments rather than rebuilding separately when release integrity matters.
Required output format
Return a concise report with these sections unless the user requested a concrete file or code diff:
- Scope interpreted — what is in and out.
- Findings / decisions — ordered by production risk, not by discovery order.
- Recommended actions — owner-ready tasks with priority and rationale.
- Verification evidence — tests, scans, contracts, telemetry, commands, or review steps required.
- Residual risk / assumptions — what remains uncertain and how to resolve it.
- Hand-offs — other capabilities that should review the work.
What ships with it
1 file 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.
- 11d ago First seen · 111 lines · 93 tokens per session scan A 153fc0f2b8c2
ci-cd-supply-chain is a skill published in the GitHub repository KyaniteLabs/checkyourself (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 93 tokens to every session and 1,228 once invoked, about $0.0005 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.
Other skills, from other repositories
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
repo-scaffold
Scaffold or standardize a production-ready repository structure with specs, source layout, tests, CI, agent context, config examples, release notes, and operational docs. Use when starting a new repo, turning a prototype into a maintainable project, adding missing repository foundations, or creating a repo skeleton…
pneuma-bansho
A board-based way to explain ideas through written Markdown, a simple text-formatting language, with the writing appearing progressively like a live lecture.
pneuma-session
Instructions for renaming an active Pneuma session and replacing its default preview with a useful title and summary. A Pneuma session is one work area inside a larger project.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
lov-npm-publisher
An npm package publishing workflow that sets up releases through GitHub Actions using OIDC, a login-free trust method, or a local granular NPM token. It covers initial setup, publishing, audit checks, and verifying the package on the npm registry.