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 gg-mo/repo-hygiene --skill using-repo-hygienegit clone --depth 1 https://github.com/gg-mo/repo-hygieneWrote 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/gg-mo/repo-hygiene/using-repo-hygiene)<a href="https://agentmods.dev/skills/gg-mo/repo-hygiene/using-repo-hygiene"><img src="https://agentmods.dev/badge/skills/gg-mo/repo-hygiene/using-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/gg-mo/repo-hygiene/using-repo-hygiene"><img src="https://agentmods.dev/badge/skills/gg-mo/repo-hygiene/using-repo-hygiene.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.00503 |
| Opus 5 | $0.00016 | $0.00251 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
using-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.
What it actually says
Using Repo Hygiene
This plugin keeps a codebase healthy as you work in it. Each sub-skill triggers on a specific moment — invoke it then via the Skill tool.
Important override: This skill set INVERTS the usual "no comments unless WHY is non-obvious" default. In a repo using this plugin, docstrings on functions and file headers ARE expected. Quality matters (see repo-hygiene:writing-docstrings); silence does not.
Trigger Table
| When this happens | Invoke |
|---|---|
| Starting substantive work in a repo you don't already understand | repo-hygiene:orienting-to-repo |
| Writing or modifying a function, class, or source file | repo-hygiene:writing-docstrings |
| About to add lines to a file >400 lines, or your edit pushes one past that | repo-hygiene:keeping-files-small |
| Changing a public API (renamed export, new flag, new route, changed signature) | repo-hygiene:keeping-docs-fresh |
| Adding business logic, branching code, or fixing a bug | repo-hygiene:testing-new-code |
| Drafting any commit message | repo-hygiene:writing-commit-messages |
| User asks to commit, merge, or push | repo-hygiene:gating-commits |
| User asks to "clean up" or apply repo-hygiene to an existing codebase | repo-hygiene:cleaning-existing-codebase |
Priority
- User instructions win. If the user says "skip the orientation," skip it.
- Coordinate with peer skill sets. If
superpowers:test-driven-developmentis already in play,testing-new-codeis satisfied by that workflow. - Otherwise apply at the triggers above.
Bypass
A user can bypass a hygiene skill for one turn with #hygiene-skip <reason> in their message. Acknowledge the bypass and proceed.
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 · 38 lines · 32 tokens per session scan A 8a75687755dd
using-repo-hygiene is a skill published in the GitHub repository gg-mo/repo-hygiene (3 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 503 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-08-31.
Other skills, from other repositories
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.