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 skills add automagik-dev/genie --skill repo-hygienegit clone --depth 1 https://github.com/automagik-dev/genieWrote 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/automagik-dev/genie/repo-hygiene)<a href="https://agentmods.dev/skills/automagik-dev/genie/repo-hygiene"><img src="https://agentmods.dev/badge/skills/automagik-dev/genie/repo-hygiene/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/automagik-dev/genie/repo-hygiene"><img src="https://agentmods.dev/badge/skills/automagik-dev/genie/repo-hygiene.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 22 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- high Anti-Refusal · line 52 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.1 | $0.00051 | $0.01320 |
| Opus 5 | $0.00026 | $0.00660 |
| Sonnet 5 | $0.00010 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
repo-hygiene 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 12d ago.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Hygiene Review
Runtime syntax: invoke the plugin copy through the active runtime's owner-qualified skill selector; use a bare selector only when intentionally selecting a user-tier copy (a separately installed personal copy; Genie no longer seeds this tier). Cross-skill prose below uses bare names as portable semantic routes; the orchestrator resolves the selector for the active runtime.
Lens
This lane audits a repository as a product whose users are contributors — its layout, history, and configuration either invite people in or quietly turn them away. Judge the repo the way its next outside contributor will experience it: clone it, look around, read the log. Commit history is documentation; branching rules are UX; every config file is a promise that must still be true.
This lane's lens is inspired by the work of Scott Chacon — GitHub co-founder, author of Pro Git, builder of GitButler.
Mandate
Assess and report by default. Apply changes only when the invocation explicitly asks (e.g. "fix", "clean up", "apply"). When you spot a finding outside this lane (architecture, security, tests), name it in one line as a handoff to the relevant lane skill under skills/ — do not investigate it yourself. When you have enough information to act, act; do not re-derive settled facts or survey options you will not pursue.
Discover the Ground Truth First
Never judge against generic convention when the repo states its own. Before any verdict, read what exists of: CLAUDE.md / AGENTS.md, README, CONTRIBUTING, the package manifest, .gitignore, git hook tooling (husky, pre-commit, commitlint or equivalents), and CI config. These define the repo's intended contracts — your job is to find where reality has drifted from them, and where a contract is missing entirely. Deliberate tradeoffs documented there (bot commits, generated files kept on purpose, submodule workflows) are design, not defects.
Genie-framework repos: if .genie/ exists, its contract is: wishes/, brainstorms/, and INDEX.md are git-tracked; genie.db (and WAL/SHM siblings) must be ignored. Verify with git check-ignore and git ls-files .genie/.
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.
- 12d ago First seen · 55 lines · 51 tokens per session scan A 8aea4709123c
repo-hygiene is a skill published in the GitHub repository automagik-dev/genie (336 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 1,320 once invoked, about $0.0003 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-30.
Other skills, from other repositories
reachable-wip-via-temporary-refs
Capture in-flight WIP via git stash create, make it reachable through temporary refs, and tear down the refs after bundling finishes.
staged-bundle-fallback-chain
Retry Git bundle creation across decreasing scopes (all, HEAD, squashed) to stay under upload size limits while keeping relevant history.
canonical-worktree-path-normalization
Resolve repo-relative paths against the canonical checkout root so shared state stays stable across Git worktrees.
empty-repo-bundle-preflight
Fail fast when the repository has no refs so downstream bundling never triggers empty Git bundles.
fast-worktree-reuse-with-head-pointer-checks
Resume existing worktrees quickly by checking stored HEAD pointers before fetching or recreating.
safe-worktree-slug-validation
Ensure Git worktree slugs can never escape the managed workspace or inject traversal.