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/securenpx skills add fmind/dot --skill securegit 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/secure)<a href="https://agentmods.dev/skills/fmind/dot/secure"><img src="https://agentmods.dev/badge/skills/fmind/dot/secure.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.00037 | $0.00914 |
| Opus 5 | $0.00018 | $0.00457 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
secure 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure a Repository
One ordered checklist that composes the tool skills; each step names the skill that owns the detail, this file only decides the order and the gate.
Checklist
- Secrets in git: run the full-history scan and wire the staged pre-commit hook per gitleaks; rotate anything found before touching anything else.
- Secrets at rest: move plaintext credentials into environment variables or encrypted
*.enc.*files per sops-secrets; runtime secrets come from Secret Manager per cloud-run. - Dependencies, IaC, licenses: run
check:vuln(native scanner) andcheck:scanper trivy; fix or justify everyHIGH/CRITICAL. - Code patterns (opt-in): adopt
check:sastper opengrep when the project handles untrusted input, authentication, or agents with tools. - Workflows: run
check:actionsand fix findings per zizmor: least-privilegepermissions, no template injection, pinned actions,persist-credentials: false. - Automated updates: enable dependabot for every ecosystem so the scans above stay green without manual bumps.
- Supply chain: for shipped images, scan, sign, and attest the digest per containerize and cosign; verification pins identity and issuer.
- Runtime posture: private services by default (
--no-allow-unauthenticated), dedicated runtime service accounts, keyless CI identity via Workload Identity Federation per cloud-run. - Threat model: when the project handles authentication, personal data, agents with tools, or public exposure, run threat-model; scanners do not find design flaws.
Gate
Every offline scan lives in mise run check so hooks and CI share it: check:leaks, check:vuln, check:scan, check:actions, and check:sast once adopted (names from mise). Full-history and image scans run in the scheduled security.yml per github-actions.
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 · 43 lines · 37 tokens per session scan A f0d94107edba
secure is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 914 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.
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.
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.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.