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.
git clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/commands/nitinjain999/platform-skills/trivy)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/trivy"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/trivy/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/commands/nitinjain999/platform-skills/trivy"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/trivy.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.00131 | $0.02345 |
| Opus 5 | $0.00066 | $0.01172 |
| Sonnet 5 | $0.00026 | $0.00469 |
| Haiku 4.5 | $0.00013 | $0.00234 |
Grade A, and why
trivy 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan for vulnerabilities, secrets, and license violations — from local dev to running cluster.
Read references/trivy.md before responding. It contains all mode logic, bootstrap steps, severity gating, output formats, .trivyignore patterns, and the Trivy Operator install via Flux HelmRelease.
Ownership boundary (enforced at the menu)
| Question | Authoritative command |
|---|---|
| "Is there a misconfig in my Terraform?" | /platform-skills:checkov |
| "Will this manifest pass admission?" | /platform-skills:kyverno apply |
| "How do I sign my image / generate an SBOM?" | /platform-skills:supply-chain |
| "Is this image safe to ship?" | this command |
| "Are there secrets in this repo?" (fast, offline pattern match) | this command |
| "Is that secret still live? What can it reach? Revoke it." | /platform-skills:kingfisher |
| "What CVEs are running in my cluster?" | this command (k8s / Operator) |
Mode dispatch
Parse the first word of $ARGUMENTS as the mode. When $ARGUMENTS is empty, run the three-layer interactive wizard.
| Mode | What it does |
|---|---|
image |
Scan a container image for OS and library CVEs |
fs |
Scan a local directory for CVEs, secrets, and license violations |
repo |
Scan a remote git repo URL (same as fs but clones first) |
secrets |
Scan current repo for hardcoded secrets only (--scanners secret) |
sbom |
Scan an existing Syft-generated SBOM file (trivy sbom <file>) |
k8s |
Live cluster image-CVE scanning via Trivy Operator (Flux HelmRelease) |
| (empty) | Three-layer interactive wizard |
Three-layer interactive wizard
Layer 1 — Developer question (intent in their language)
What are you trying to find out?
1. "Is this image safe to ship?" → image CVE scan
2. "Are there secrets in this repo/code?" → secret scan
3. "What's the full risk of this checkout?" → fs scan (vuln + secret + license)
4. "What's running vulnerable in my cluster?" → live cluster scan (Operator)
5. "Is this SBOM vulnerable?" → SBOM scan (Syft output)
IaC misconfig? → /platform-skills:checkov
Will this manifest pass admission? → /platform-skills:kyverno apply
Image signing / SBOM generation? → /platform-skills:supply-chain
Enter 1–5 or mode name:
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 · 231 lines · 131 tokens per session scan A 5c421f3456c0
trivy is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed 2d ago), licensed Apache-2.0. It adds 131 tokens to every session and 2,345 once invoked, about $0.0007 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 commands, from other repositories
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
devops
DevOps and infrastructure with Masao (CI/CD, Docker, cloud).
aw-author
Author, validate, or improve GitHub Agentic Workflow (gh-aw) markdown files.
sparc-devops
🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…