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 strikersam/autonomous-ai-agency --skill git-hygienegit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/git-hygiene)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/git-hygiene"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/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/strikersam/autonomous-ai-agency/git-hygiene"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/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.00044 | $0.00542 |
| Opus 5.5 | $0.00018 | $0.00217 |
| Sonnet 5.5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Git Hygiene
Purpose
Ensures the repository's git history, branch state, and commit messages are clean, meaningful, and follow project conventions before pushing or merging.
When to Use
- Before pushing commits to master or opening a PR
- When git history has become messy (fixup commits, WIP messages, etc.)
- As a final step in any implementation workflow
- When the
changelog-enforcerorrelease-readinessskills are applied
Process
1. Review Staged and Unstaged Changes
- Run
git statusto see what's changed - Confirm no unintended files are staged (build artifacts, secrets, editor files)
- Check
.gitignoreis catching what it should
2. Review Commit History
- Run
git log --oneline -20to inspect recent commits - Flag commits with vague messages: "fix", "wip", "test", "asdf", etc.
- Note commits that could be squashed without losing meaning
3. Validate Commit Messages
- Ensure messages follow the pattern:
<type>: <short description> [#issue] - Valid types:
feat,fix,docs,chore,refactor,test,style - Subject line should be ≤72 characters
- No trailing periods in subject line
4. Clean Up if Needed
- Squash fixup commits with
git rebase -iif appropriate - Amend the most recent commit message with
git commit --amendif needed - Do not rewrite history on shared branches unless explicitly authorized
5. Confirm Branch State
- Ensure the working branch is up to date with its upstream
- Resolve any merge conflicts before pushing
- Confirm you are on the intended branch
6. Push
- Push with
git push origin <branch> - Use
--force-with-leaseonly if a rebase was performed, never--force
Output
- Clean git history with meaningful commit messages
- No unintended files committed
- Successful push to the correct branch
Notes
- Never commit secrets, credentials, or API keys
- Binary files and generated files should generally not be committed
- If in doubt about a commit, use
git diff HEAD~1to review what it contains
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.
- 7d ago Changed · +4 lines · +44 tokens per session 70bdf3bf7157
- 1mo ago First seen · 53 lines · 0 tokens per session scan A d2aacc93d9f4
git-hygiene is a skill published in the GitHub repository strikersam/autonomous-ai-agency (11 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 542 once invoked, about $0.0002 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
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.