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 Zate/cc-plugins --skill git-hygienegit clone --depth 1 https://github.com/Zate/cc-pluginsWrote 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/zate/cc-plugins/git-hygiene)<a href="https://agentmods.dev/skills/zate/cc-plugins/git-hygiene"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/git-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/zate/cc-plugins/git-hygiene"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/git-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.00029 | $0.01162 |
| Opus 5.5 | $0.00012 | $0.00465 |
| Sonnet 5.5 | $0.00006 | $0.00232 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
git-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 1mo 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Hygiene
Branching, commit, and merge practices wired to the devloop workflow.
Devloop Integration
Configure git behavior in .devloop/local.md:
---
git:
auto-branch: true # Create branch when plan starts
branch-pattern: "feat/{slug}"
pr-on-complete: ask # ask | always | never
commits:
style: conventional # conventional | simple
---
Related commands:
/devloop:ship— commit with plan context, create PR/devloop:pr-feedback— integrate PR review comments into plan.md
Plan tasks map to commits. /devloop:ship offers:
- Single commit — squash all completed tasks into one.
- Atomic commits — one commit per task, using the task description as the message subject.
Plan task example:
- [x] Task 1.1: Create config skill
- [x] Task 1.2: Add parsing script
- [x] Task 1.3: Update session hook
Atomic equivalent:
feat(devloop): create local-config skill
feat(devloop): add config parsing script
feat(devloop): update session-start hook
Commit Principles
- One logical change per commit — a reviewer should understand the diff in isolation.
- Commit compiles and tests pass — never check in broken WIP on a shared branch.
- Message explains "why", not "what" — the diff already shows what.
Size guidelines
| Size | Lines | When |
|---|---|---|
| XS | <50 | Single fix, config change |
| S | 50–200 | One feature, one refactor |
| M | 200–500 | Feature with tests |
| L | >500 | Consider splitting |
Devloop tasks typically land in the S–M range.
Split strategy for large changes
Rather than one mega-commit:
- Refactor / preparation commit
- Core implementation commit
- Tests commit
- Docs commit
Or, inside devloop: one commit per phase.
Anti-patterns
- WIP commits with broken code on shared branches
- Mixing refactor + feature + fix in one commit
- "fix everything" catch-all commits
- Unrelated changes bundled
Conventional Commits
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.
- 1mo ago First seen · 160 lines · 29 tokens per session scan A 1441481e4492
git-hygiene is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,162 once invoked, about $0.0001 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.