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 agentmods add skills/fmind/dotfiles/security-scannpx skills add fmind/dotfiles --skill security-scangit clone --depth 1 https://github.com/fmind/dotfilesWhat 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 | $0.00034 | $0.01867 |
| Opus 5 | $0.00017 | $0.00933 |
| Sonnet 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 yesterday.
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.
- yesterday 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 2d ago), licensed MIT. It adds 34 tokens to every session and 1,867 once invoked, about $0.0002 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-31.
Other skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
obsidian-bases
Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.
telegram
Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…
chezmoi-expert
Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…