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/checkov)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/checkov"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/checkov/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/checkov"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/checkov.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.00103 | $0.01224 |
| Opus 5 | $0.00051 | $0.00612 |
| Sonnet 5 | $0.00021 | $0.00245 |
| Haiku 4.5 | $0.00010 | $0.00122 |
Grade A, and why
checkov 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap Checkov and scan Terraform code for security misconfigurations — locally, before CI catches them.
Read references/checkov.md before responding. It contains all mode logic, bootstrap steps, provider detection, and fix patterns.
Mode dispatch
Parse the first word of $ARGUMENTS as the mode. When $ARGUMENTS is empty, run the interactive wizard.
| Mode | What it does |
|---|---|
static |
Scan .tf source files with --download-external-modules true |
plan |
terraform init → plan → JSON → Checkov --deep-analysis (use --upgrade flag to also upgrade providers) |
secrets |
Scan entire repo for hardcoded secrets (--framework secrets --enable-secret-scan-all-files) |
audit |
One-time secrets history scan across all commits (--scan-secrets-history) |
multi |
Scan Terraform + GitHub Actions + Dockerfiles + Helm in a single run |
baseline |
Create .checkov.baseline to snapshot existing violations |
fix |
Re-run scan and apply AI-generated patches to .tf files |
scaffold |
Generate .checkov.yaml config (SOC 2 / CIS / PCI / HIPAA variants) and/or custom-checks/ |
| (empty) | Interactive wizard — ask Q1 (mode) then Q2 (path/context) |
Interactive Wizard
Q1 — Mode?
What do you need?
1. static — scan .tf source files [default]
2. plan — terraform plan → Checkov deep analysis
3. secrets — scan entire repo for hardcoded secrets and tokens
4. audit — one-time scan of git commit history for leaked secrets
5. multi — scan Terraform + GitHub Actions + Dockerfiles + Helm together
6. baseline — snapshot existing violations (first-run brownfield)
7. fix — scan and apply AI-generated fixes to .tf files
8. scaffold — generate .checkov.yaml (SOC 2 / CIS / PCI / HIPAA) or custom-checks/
Enter 1–8 or mode name:
Q2 — Path? (ask after Q1)
Terraform root directory, or press Enter to scan current directory [default: .]:
Then proceed into the relevant mode section in references/checkov.md.
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 · 90 lines · 103 tokens per session scan A 599e0ff2cbcc
checkov is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 103 tokens to every session and 1,224 once invoked, about $0.0005 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
ia-verify
Run pre-PR verification chain -- build, types, lint, tests, security scan, diff review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
release
Generate changelog, bump version, and create git tag.
ia-report-bug
Report a bug in the whetstone plugin.
cccs-guidance
CCCS assessment process and certified cloud provider guidance.
environment-switching-local-cloud-ssh
The environment selector at the bottom of Claude Code switches where work executes: local for fast interactive iteration, cloud (Anthropic servers) for routines that must run with your machine off, SSH for driving a remote box like a VPS.