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/project-healthnpx skills add fmind/dot --skill project-healthgit 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/project-health)<a href="https://agentmods.dev/skills/fmind/dot/project-health"><img src="https://agentmods.dev/badge/skills/fmind/dot/project-health.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.00038 | $0.00734 |
| Opus 5 | $0.00019 | $0.00367 |
| Sonnet 5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
project-health 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Health
The recurring pass that makes an existing repository current, consistent, simple, and working; it fixes in place and proves the result with the gate. repository-review owns the read-only audit with ranked findings; deployments, registries, and external services stay out of scope.
Workflow
- Baseline: record
git status --short, thenmise run checkandmise run testas they stand; fix a red baseline first so later regressions are attributable. - Toolchain and dependencies: bump one ecosystem at a time and validate between each per upgrade-tools.
- Stack conformance: layout, tooling, and tasks match the stack skill (go-stack, python-stack, typescript-stack).
- Tasks and hooks:
mise.tomlexposes the canonical task vocabulary per mise; hooks and CI call those tasks per lefthook and github-actions. - Complexity: remove dead code, duplicated logic, stale config, and unused dependencies per reduce-complexity.
- Security: run the offline scans wired into
mise run checkper secure:check:leaks,check:scan,check:vuln,check:sast,check:actions. - Docs: sync
README.mdandAGENTS.mdper readme-agents; trim wider docs per improve-docs. - Agent files: promote repeated instructions into
.agents/skills/per skillify. - Final gate: Run the full gate (
mise run all); if the tree carries unrelated changes and the gate write-formats, run it in a temporarygit worktreeor fall back tomise run checkandmise run test(see mise). - Report: what changed per area (the tree holds only intended changes), what was left alone and why, and the highest proven rung of the proof ladder.
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 · 33 lines · 38 tokens per session scan A 6cda1ef62828
project-health is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 734 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.