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/repository-reviewnpx skills add fmind/dot --skill repository-reviewgit 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/repository-review)<a href="https://agentmods.dev/skills/fmind/dot/repository-review"><img src="https://agentmods.dev/badge/skills/fmind/dot/repository-review.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.00040 | $0.00965 |
| Opus 5 | $0.00020 | $0.00483 |
| Sonnet 5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
repository-review 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Review
Audit the whole delivery system read-only and report ranked, evidence-backed findings; diff-review owns one change, project-backlog turns findings into issues, and project-health applies the fixes.
Workflow
- Scope the review: Read the repository instructions and the stack, CI, security, or documentation skills the requested dimensions need; confirm which live systems are authorized and treat every other credential, cluster, project, deployment, or release as unavailable.
- Record the candidate: Capture branch,
HEAD, upstream, andgit status --short; distinguish staged, unstaged, and untracked paths, treat pre-existing changes as user-owned, and state whether evidence concerns committedHEAD, the dirty tree, or both. - Map the system: Inspect manifests, entry points, package boundaries, tasks, hooks, workflows, deployment and release automation, docs, generated files, and runtime configuration against the review matrix.
- Run native checks: Iterate with
mise run check, targetedcheck:*subtasks, andmise run test; invoke secure only when the request needs the full security boundary. - Gate the candidate: 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). - Inspect live evidence read-only: Compare the exact
HEADSHA with CI checks, deployments, tags, releases, or runtime observations only where authorized and reachable; a green result for another head is stale. - Challenge each conclusion: Reproduce high-impact claims when safe, prefer repository or dependency source over assumptions, and separate an observed defect from a speculative risk.
- Report findings: Lead with Key findings ranked
P0–P3(scale in diff-review), each with the defect, impact, and direct file, command, CI, or runtime evidence; if none are material, say so and list residual gaps. - State proof and actions: Report the highest proven rung of the proof ladder with each check marked pass, fail, blocked, or not run, then list Actions by priority, each starting with a verb and naming the owner or required authority.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 40 lines · 40 tokens per session scan A eaf4f739c7e8
repository-review is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 965 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.