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 balsm-health/Balsm-AI --skill detecting-supply-chain-attacks-in-ci-cdgit clone --depth 1 https://github.com/balsm-health/Balsm-AIWrote 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/balsm-health/balsm-ai/detecting-supply-chain-attacks-in-ci-cd)<a href="https://agentmods.dev/skills/balsm-health/balsm-ai/detecting-supply-chain-attacks-in-ci-cd"><img src="https://agentmods.dev/badge/skills/balsm-health/balsm-ai/detecting-supply-chain-attacks-in-ci-cd/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/balsm-health/balsm-ai/detecting-supply-chain-attacks-in-ci-cd"><img src="https://agentmods.dev/badge/skills/balsm-health/balsm-ai/detecting-supply-chain-attacks-in-ci-cd.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.00069 | $0.00648 |
| Opus 5.5 | $0.00028 | $0.00259 |
| Sonnet 5.5 | $0.00014 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
detecting-supply-chain-attacks-in-ci-cd 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 92 lines · 69 tokens per session scan A 4a6a80849280
detecting-supply-chain-attacks-in-ci-cd is a skill published in the GitHub repository balsm-health/Balsm-AI (2 stars, last pushed 21d ago), with no licence file. It adds 69 tokens to every session and 648 once invoked, about $0.0003 per session on Opus 5.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
github-hardening
Review or update GitHub repository hardening guidance and its Terraform implementation under config/infra, including rulesets, required checks, scanning, permissions, provider pins, and plan/apply safety. Do not use for ordinary app code, generic template adaptation, release integrity, or routine workflow validation.
repo-adaptation
Adapt the template to project code, language and framework needs, or optional Go, Node.js, Python, SQL, and polyglot guidance. Covers dependencies, runtime behavior, Docker, Makefile targets, and customization surfaces. Do not use for routine bug fixes, pure workflow validation, GitHub hardening, or…
repo-security-review
Manual-only skill. Use ONLY when the user explicitly invokes: $repo-security-review (Codex) or /repo-security-review (Claude Code) Never select this skill via semantic matching.
pr-draft-summary
Draft a concise pull request handoff after substantive repository changes are finished or ready for review. Trigger when wrapping up code, test, script, workflow, release, security, documentation-with-behavior-impact, or template customization changes and the user needs a PR title/body grounded in the real diff…
release-integrity
Use when reviewing or improving this template's release-integrity story, including artifact verification, SBOMs, attestations, vulnerability scanning, signing guidance, and release-workflow safety. Do not use for general CI validation, GitHub-settings-only work, or unrelated template customization.
workflow-validation
Use when validating repository workflows after changes to Docker-first Makefile targets, Dockerfiles, scripts, CI, release packaging, smoke tests, or documentation alignment. Do not use for repo redesign, GitHub-policy-only changes, or instruction-only skill edits with no workflow impact.