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/dot/gitleaksnpx skills add fmind/dot --skill gitleaksgit clone --depth 1 https://github.com/fmind/dotWrote 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/dot/gitleaks)<a href="https://agentmods.dev/skills/fmind/dot/gitleaks"><img src="https://agentmods.dev/badge/skills/fmind/dot/gitleaks.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.00783 |
| Opus 5 | $0.00020 | $0.00392 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
gitleaks 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 today.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gitleaks
Find credentials before they reach a remote and the ones that already did; each scope answers a different question, and secure orders the pass.
Commands
gitleaks git --staged --verbose # pre-commit: the change about to be committed
gitleaks git --log-opts="--max-count=100" --verbose # check:leaks: the recent commits (bounded, fast)
gitleaks git --verbose # full history: the scheduled audit
gitleaks dir . --verbose # working tree, including untracked files
gitleaks git --redact=100 --report-format sarif --report-path gitleaks.sarif
Mise Task
Expose a scope-aware scan as check:leaks per mise: scan the working tree before the repository has a commit, retain the bounded history scan afterward, and forward --staged from the pre-commit hook in lefthook:
[tasks."check:leaks"]
description = "Audit staged changes, the working tree, or recent commits for leaked secrets (gitleaks)"
run = """
sh -c '
if [ "$#" -gt 0 ]; then
gitleaks git --verbose "$@"
elif git rev-parse --verify HEAD >/dev/null 2>&1; then
gitleaks git --log-opts="--max-count=100" --verbose
else
gitleaks dir . --verbose
fi
' --
"""
When a Secret Is Found
- Rotate first: a secret in history is compromised even after the commit disappears.
- Remove it from the source: move the value to an environment variable or an encrypted file per sops-secrets.
- Rewrite history only when asked: rewrites affect every clone; confirm with the user before
git filter-repo. - Allowlist true false positives with an inline
gitleaks:allowcomment or a rule in.gitleaks.toml, each with a reason.
Gotchas
- Shallow CI checkouts: fetch the depth the task scans (
fetch-depth: 100) and keep the full-history audit in the scheduledsecurity.ymljob atfetch-depth: 0per github-actions. - Fresh repository: the task uses
gitleaks diruntilHEADexists, avoiding a misleading Git error while still scanning untracked files;--stagedkeeps pre-commit scoped to the index. --redactin shared logs: never print a found secret in CI output or an uploaded report.
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.
- today Changed · +10 lines 5edd608da7a6
- yesterday First seen · 53 lines · 41 tokens per session scan A 3e8be6fcbe72
gitleaks is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 783 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
mise
Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.