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 Njones17/AI-agent-master-cyber-skills-list --skill implementing-image-provenance-verification-with-cosigngit clone --depth 1 https://github.com/Njones17/AI-agent-master-cyber-skills-listWrote 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/njones17/ai-agent-master-cyber-skills-list/implementing-image-provenance-verification-with-cosign)<a href="https://agentmods.dev/skills/njones17/ai-agent-master-cyber-skills-list/implementing-image-provenance-verification-with-cosign"><img src="https://agentmods.dev/badge/skills/njones17/ai-agent-master-cyber-skills-list/implementing-image-provenance-verification-with-cosign/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/njones17/ai-agent-master-cyber-skills-list/implementing-image-provenance-verification-with-cosign"><img src="https://agentmods.dev/badge/skills/njones17/ai-agent-master-cyber-skills-list/implementing-image-provenance-verification-with-cosign.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.00040 | $0.02167 |
| Opus 5 | $0.00020 | $0.01084 |
| Sonnet 5 | $0.00008 | $0.00433 |
| Haiku 4.5 | $0.00004 | $0.00217 |
Grade B, and why
implementing-image-provenance-verification-with-cosign scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo mv cosign-linux-amd64 /usr/local/bin/cosign Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -O -L "https://github.com/sigstore/cosign/releases/latest/download/cosign-linux-amd64" 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
4 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 · 306 lines · 40 tokens per session scan B 47082426470d
implementing-image-provenance-verification-with-cosign is a skill published in the GitHub repository Njones17/AI-agent-master-cyber-skills-list (21 stars, last pushed 6mo ago), with no licence file. It adds 40 tokens to every session and 2,167 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
implementing-image-provenance-verification-with-cosign
Sign and verify container image provenance using Sigstore Cosign with keyless OIDC-based signing, attestations, and Kubernetes admission enforcement.
verifying-build-provenance-with-slsa-sigstore
Verify signed artifacts and SLSA build provenance with Sigstore cosign and slsa-verifier, enforce keyless OIDC identity, and apply SLSA Build levels to harden the software supply chain.
implementing-supply-chain-security-with-in-toto
Implement software supply chain integrity verification for container builds using the in-toto framework to create cryptographically signed attestations across CI/CD pipeline steps.
Supply Chain Security
Software supply chain security — SBOM generation and analysis, dependency confusion and typosquatting detection, malicious package indicators, CI/CD pipeline hardening, and artifact provenance/signing (SLSA, Sigstore).
supply-chain-security-expert
Secure the path from dependency to deployed artefact: SBOMs, dependency scanning, build provenance, artefact signing and CI/CD integrity. Use when the user mentions supply chain security, SBOM, CycloneDX or SPDX, SCA or dependency scanning, Sigstore or cosign, SLSA, provenance and attestation, a compromised or…
securing-container-registry-images
Securing container registry images by implementing vulnerability scanning with Trivy and Grype, enforcing image signing with Cosign and Sigstore, configuring registry access controls, and building CI/CD pipelines that prevent deploying unscanned or unsigned images.