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 slsa-provenancegit 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/slsa-provenance)<a href="https://agentmods.dev/skills/sbom-tool/gh-guard/slsa-provenance"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/slsa-provenance/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/slsa-provenance"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/slsa-provenance.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.00026 | $0.01391 |
| Opus 5 | $0.00013 | $0.00696 |
| Sonnet 5 | $0.00005 | $0.00278 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
slsa-provenance 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 10d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLSA L3 Provenance for Rust Crates
SLSA (Supply-chain Levels for Software Artifacts) Level 3 provides verifiable build provenance — a signed attestation of what was built, from what source, by which builder. This skill covers the three-job pipeline architecture for Rust crates.
Architecture
The publish workflow uses three sequential jobs:
publish ──→ provenance ──→ release
│ │ │
├─ Tests ├─ SLSA L3 ├─ Download provenance
├─ Verify tag │ generator ├─ Create GitHub Release
├─ Package │ (reusable) └─ Attach .intoto.jsonl
├─ Hash .crate │
├─ Auth OIDC │
└─ Publish │
│
Generates signed
.intoto.jsonl
attestation
Job 1: publish
- Checks out code with
fetch-depth: 0(needed for ancestry verification) - Verifies tag matches
Cargo.tomlversion - Verifies tagged commit is ancestor of
origin/main - Runs tests and cargo-deny
- Packages the crate (
cargo package --locked) - Generates SHA-256 hash of the
.cratefile - Authenticates via OIDC and publishes
Output: hashes — base64-encoded SHA-256 subject hashes
Job 2: provenance
- Uses the SLSA GitHub generator reusable workflow
- Takes the hash subjects from the publish job
- Generates a signed
.intoto.jsonlattestation (DSSE envelope) - Uploads as a workflow artifact
Critical constraints:
- MUST use
@tagreference (e.g.,@v2.1.0), not SHA — the reusable workflow requires this - Uses
upload-assets: falsebecause we attach provenance to the release ourselves (needed for immutable releases)
Job 3: release
- Downloads the provenance artifact from the previous job
- Creates a GitHub Release with the
.intoto.jsonlfile attached - Uses
--verify-tagto ensure the tag exists
Critical constraint for immutable releases:
If your GitHub org has "immutable releases" enabled, you CANNOT upload assets after a release is created. The provenance file must be attached AT creation time, which is why this job downloads the artifact first, then creates the release with it in a single gh release create call.
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.
- 10d ago First seen · 145 lines · 26 tokens per session scan A aa85e40304fa
slsa-provenance is a skill published in the GitHub repository sbom-tool/gh-guard (15 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 1,391 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
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.