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 fmind/dotfiles --skill security-scangit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/fmind/dotfiles/security-scan)<a href="https://agentmods.dev/skills/fmind/dotfiles/security-scan"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/security-scan/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/fmind/dotfiles/security-scan"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/security-scan.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.00034 | $0.01867 |
| Opus 5.5 | $0.00014 | $0.00747 |
| Sonnet 5.5 | $0.00007 | $0.00373 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
security-scan 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanning
Scan a repository (and its images) for vulnerabilities, misconfigurations, secrets, and license issues. Layers Trivy (config: dot_config/trivy/trivy.yaml — HIGH/CRITICAL, ignore-unfixed, scanners: vuln/misconfig/secret/license) over gitleaks for deep git-history secret detection, complementing the language-native scanners (govulncheck, pip-audit).
Workflow
- Repository scan (dependencies, misconfig, secrets, licenses in one pass):
trivy --config trivy.yaml fs . # always pass --config: an exported TRIVY_CONFIG outranks ./trivy.yaml — see Gotchas - Targeted config scan (Dockerfiles, Kubernetes manifests, Terraform — optional if already done via
trivy fs):trivy --config trivy.yaml config . - Secrets in git history (deeper than a working-tree scan — catches committed-then-deleted secrets):
mise run check:leaks # recent commits (this repo caps at the last 10) mise run check:leaks --staged # pre-commit scope gitleaks git --verbose # full history — the actual audit - Container image scan (after a build — see containerize):
trivy --config trivy.yaml image <registry>/<image>:<tag> - Language-native depth (already wired into
mise run checkascheck:vuln):- Go:
go tool govulncheck ./... - Python:
uv run pip-audit
- Go:
- Triage: summarize findings by severity, separate fixable from
unfixed, and propose the minimal upgrade/patch or a justified ignore.
Mise Task Integration
Expose security scans in the project's canonical task vocabulary (mise.toml) per the mise skill. check:leaks (gitleaks) and check:scan (trivy fs, one pass over vuln/misconfig/secret/license) follow the same pattern in every repo; check:vuln is the language-native scanner where one exists (govulncheck/pip-audit — see go-stack/python-stack) and is omitted entirely in polyglot or config-only repos with no native scanner — check:scan's trivy fs already covers vulnerabilities there:
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 · 88 lines · 34 tokens per session scan A 3cbe142d62f9
security-scan is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,867 once invoked, about $0.0001 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-31.
Other skills, from other repositories
airflow
Develop and test Airflow DAGs with the Astronomer astro CLI.
docker
Run Docker, Compose, and Colima; build, scan, sign, and verify Python images.
kubernetes
Operate Kubernetes with kubectl, Helm, k9s, kustomize, and stern.
full-review
Full review: read every repo area, apply verified fixes, and prove all checks pass.
duckdb
Query and export CSV, Parquet, JSON, or SQLite data with DuckDB.
observability
Instrument Python services and agents: structlog logs, OpenTelemetry traces and metrics.