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 sbom-tool/gh-guard --skill ci-pipelinegit clone --depth 1 https://github.com/sbom-tool/gh-guardWrote 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/sbom-tool/gh-guard/ci-pipeline)<a href="https://agentmods.dev/skills/sbom-tool/gh-guard/ci-pipeline"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/ci-pipeline/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/sbom-tool/gh-guard/ci-pipeline"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/ci-pipeline.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.00021 | $0.01545 |
| Opus 5 | $0.00010 | $0.00772 |
| Sonnet 5 | $0.00004 | $0.00309 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
ci-pipeline 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.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust CI Pipeline Best Practices
This skill covers the design patterns for a robust Rust CI pipeline, based on production experience with multi-job workflows.
Six-Job Architecture
lint ──┐
msrv ──┤
test ──┼──→ ci (gate)
deny ──┤
audit ─┘
| Job | Purpose | Blocking? |
|---|---|---|
lint |
cargo fmt --check + cargo clippy (default + all features) |
Yes |
msrv |
cargo check --locked with pinned MSRV toolchain |
Yes |
test |
cargo test across OS matrix (Linux/macOS/Windows) + beta |
Yes |
deny |
cargo-deny for advisories, bans, licenses, sources | Mixed* |
audit |
cargo audit for known vulnerabilities |
Yes |
ci |
Gate job — single required status check | Always runs |
*deny uses continue-on-error for advisories (informational) but blocks on bans/licenses/sources.
Gate Job Pattern
The ci gate job is the only required status check in branch protection settings:
ci:
name: CI
if: always()
needs: [lint, msrv, test, deny, audit]
runs-on: ubuntu-latest
steps:
- name: Evaluate results
run: |
result="${{ contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled') }}"
[[ "$result" == "false" ]] || exit 1
Why this pattern:
- Adding/removing jobs doesn't require updating branch protection
if: always()ensures the gate runs even if upstream jobs are cancelled- Single check to configure in GitHub Settings
Action SHA Pinning
All actions MUST be pinned to full commit SHA with a version comment:
# v6.0.2
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
Why SHA not tag:
- Tags can be moved (force-pushed) by the action owner or an attacker with write access
- SHA is immutable — ensures reproducible builds
- Scorecard checks for this (Pinned-Dependencies)
Real-world incident — Trivy tag hijacking (March 2026):
Attackers with write access to aquasecurity/trivy-action force-pushed 75 of 76 version tags to point to malicious commits. The poisoned entrypoint.sh harvested secrets from CI runner process memory and exfiltrated them to a typosquatting C2 domain (scan.aquasecurtiy[.]org). Over 10,000 workflow files on GitHub referenced aquasecurity/trivy-action by tag. Any pipeline that ran a poisoned tag had all accessible secrets stolen. SHA-pinned workflows were completely unaffected — the immutable commit reference couldn't be redirected. This incident is the single strongest argument for SHA pinning.
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 · 195 lines · 21 tokens per session scan A 8ea0e6d40d8b
ci-pipeline is a skill published in the GitHub repository sbom-tool/gh-guard (15 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 1,545 once invoked, about $0.0001 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
rust-crate-ci
Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.
rust-tooling-cicd
Use when structuring a Cargo workspace or building a Rust CI pipeline — fmt, clippy, cargo-deny/audit, nextest, coverage, MSRV. Not for writing the tests themselves (rust-testing-quality).
cargo-workflows
Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.
cargo-workflows
Cargo workflow skill for Rust projects. Use when managing workspaces, feature flags, build scripts, cargo cache, incremental builds, dependency auditing, or CI configuration with Cargo. Activates on queries about cargo workspaces, Cargo.toml features, build.rs, cargo nextest, cargo deny, cargo check vs build, or…
scaffold-rust-cli
Scaffold a complete Rust CLI project with Cargo, cargo-deny, cargo-nextest, git-cliff, GitHub Actions CI/CD, and Makefile. Use when the user says "scaffold a Rust CLI", "new Rust CLI", "create a Rust binary crate", "start a Rust CLI", "bootstrap a Rust CLI", or starts a Rust command-line tool from scratch. Optionally…
rust-ci-setup
Set up a CI/CD pipeline for Rust projects. Use when: creating CI for Rust, adding Clippy/fmt/test/audit to CI. Do not use: for local development setup, non-CI automation.