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 scorecard-checksgit 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/scorecard-checks)<a href="https://agentmods.dev/skills/sbom-tool/gh-guard/scorecard-checks"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/scorecard-checks/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/scorecard-checks"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/scorecard-checks.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.00019 | $0.02554 |
| Opus 5 | $0.00010 | $0.01277 |
| Sonnet 5 | $0.00004 | $0.00511 |
| Haiku 4.5 | $0.00002 | $0.00255 |
Grade A, and why
scorecard-checks 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Last updated: 2026-03-10 — Scorecard checks evolve; verify against the latest Scorecard docs if scores seem unexpected.
OpenSSF Scorecard Checks for Rust Projects
The OpenSSF Scorecard evaluates 18 security checks on a 0-10 scale. This skill covers each check with Rust-specific guidance for maximizing your score.
Quick Reference
| Check | Key Files | Scorecard Impact | Difficulty |
|---|---|---|---|
| Security-Policy | SECURITY.md |
+1 | Easy |
| License | LICENSE |
+1 | Easy |
| Binary-Artifacts | — (avoid committing binaries) | +1 | Easy |
| Dangerous-Workflow | .github/workflows/*.yml |
+1 | Easy |
| Token-Permissions | .github/workflows/*.yml |
+1 | Medium |
| Pinned-Dependencies | .github/workflows/*.yml |
+1 | Medium |
| Branch-Protection | GitHub Settings | +1 | Medium |
| CI-Tests | .github/workflows/ci.yml |
+1 | Medium |
| Dependency-Update-Tool | .github/dependabot.yml OR renovate.json |
+1 | Easy |
| Fuzzing | fuzz/ + CI workflow, OR OSS-Fuzz integration |
+1 | Medium |
| SAST | .github/workflows/codeql.yml |
+1 | Easy |
| Vulnerabilities | osv-scanner.toml, Cargo.lock |
+1 | Variable |
| Code-Review | PR review settings | +1 | Behavioral |
| Contributors | — (multiple contributors) | +1 | Organic |
| Maintained | — (recent commits, issues) | +1 | Organic |
| Packaging | publish.yml |
+1 | Medium |
| Signed-Releases | GitHub Releases + provenance | +1 | Hard |
| CII-Best-Practices | bestpractices.dev badge | +0.5 | Manual |
Detailed Check Guidance
1. Security-Policy (Easy — 10/10)
What it checks: Presence of SECURITY.md in repo root or .github/.
Rust action: Use the templates/SECURITY.md template. Include coordinated disclosure policy and supported versions table.
2. License (Easy — 10/10)
What it checks: Recognized license file in repo root.
Rust action: Add LICENSE (MIT or Apache-2.0 are standard for Rust). Ensure Cargo.toml has matching license = "MIT".
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 · 158 lines · 19 tokens per session scan A 4bba0e49b5ae
scorecard-checks is a skill published in the GitHub repository sbom-tool/gh-guard (15 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 2,554 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
apiiro-mcp-secure-prompt
Use the Apiiro MCP tool apiirosecureprompt when Apiiro MCP is configured in the client and the user wants security guidance added to a coding task before implementation. Trigger on secure-prompt via MCP, or when the user asks for security-aware prompt enhancement before coding (auth, new APIs, persistence, secrets…
implementing-github-advanced-security-for-code-scanning
Configure GitHub Advanced Security with CodeQL to perform automated static analysis and vulnerability detection across repositories at enterprise scale.
bob-egress
List, add, test, enable, disable, or remove Hacker Bob egress profiles from Codex.
detecting-typosquatting-packages
Flag misspelled, brandjacked, and typosquatted package names across npm, PyPI, and crates.io before installation using edit-distance, keyboard-proximity, and known-target corpus matching with typomania, OSSGadget, and pypi-scan.
security-expert
Expert-level application security, OWASP Top 10, penetration testing, and security best practices. Use when the user mentions OWASP, pentesting, appsec, vulnerability, encryption, or authentication, or when the task involves Security Principles, OWASP Top 10, Security Domains, or Broken Access Control.
codeinspectus-fix-one
Investigate and remediate exactly one user-selected CodeInspectus finding with evidence-gated reproduction, a separately approved minimal patch, focused regression testing, and an exact-prior-scan rescan. Use when a user asks an agent to examine, reproduce, fix, or verify one CodeInspectus finding without batching…