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 Cloudgeni-ai/opengeni --skill checkovgit clone --depth 1 https://github.com/Cloudgeni-ai/opengeniWrote 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/cloudgeni-ai/opengeni/checkov)<a href="https://agentmods.dev/skills/cloudgeni-ai/opengeni/checkov"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/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/skills/cloudgeni-ai/opengeni/checkov"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/checkov.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00379 |
| Opus 5.5 | $0.00015 | $0.00152 |
| Sonnet 5.5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
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 1mo 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.
What it actually says
Checkov
Use this skill when the user asks to scan Terraform or infrastructure-as-code for security, compliance, or best-practice issues.
Workflow
- Confirm the repository path before scanning. Repository resources are usually mounted under
/workspace/repos/<host>/<owner>/<repo>; use the session's resolved resource path instead of guessing. - Run Checkov from the repository root or the relevant Terraform subdirectory:
checkov -d . --framework terraform --compact
- For a machine-readable result that is easier to inspect and summarize, write JSON to a temporary file:
checkov -d . --framework terraform -o json --output-file-path /tmp/checkov-results
- Summarize the failed checks in plain language. Include the check ID, file, resource, and reason.
- When the user asks for fixes, edit only the selected findings. Keep changes focused and preserve the existing Terraform style.
- Validate after edits:
terraform fmt -recursive
terraform init -backend=false
terraform validate
checkov -d . --framework terraform --compact
- If GitHub credentials are available, create a branch and draft pull request for the fix.
Guardrails
- Do not run
terraform applyunless the user explicitly asks for it. - Prefer
terraform init -backend=falsefor validation so remote state is not touched. - Do not suppress Checkov findings unless the user asks for a suppression and the reason is documented in code.
- If provider credentials are missing, still run static checks and explain which validation steps could not be completed.
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.
- 1mo ago First seen · 44 lines · 38 tokens per session scan A 0e8234d9c4b8
checkov is a skill published in the GitHub repository Cloudgeni-ai/opengeni (205 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 379 once invoked, about $0.0002 per session on Opus 5.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
playwright
Use when the task requires capturing or automating a real browser from the terminal.
effect-v4
Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to [email protected] — Context.Service and explicit layers, Schema.TaggedError and typed recovery, the effect/cli command surface, and the vendored effect source oracle. Use when writing…
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
ax-cpp-gen
Use when writing C++ code with axllm for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
ax-java-gen
Use when writing Java code with dev.axllm:ax for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
ax-go-flow
Use when writing Go code with github.com/ax-llm/ax/packages/go for flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components.