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 codebygarv/Ai-skills --skill git-hook-automation-designergit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/git-hook-automation-designer)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/git-hook-automation-designer"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/git-hook-automation-designer/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/codebygarv/ai-skills/git-hook-automation-designer"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/git-hook-automation-designer.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.00039 | $0.00425 |
| Opus 5 | $0.00019 | $0.00212 |
| Sonnet 5 | $0.00008 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
git-hook-automation-designer 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 5d 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
Purpose
Design fast, unobtrusive client-side Git hooks using Husky, Lefthook, or pre-commit to automatically run lint-staged formatting, branch naming enforcement, secret detection, and commit message linting before code leaves the developer's machine.
When to Use
- Preventing broken code, unformatted files, and accidental secret keys from being pushed to GitHub.
- Standardizing Conventional Commits across team members (
commitlint). - Accelerating local feedback so CI doesn't fail on trivial formatting mistakes.
What to Analyze
- Hook Framework Selection: Lefthook (super-fast parallel execution in Go/binary) vs Husky + lint-staged (standard Node ecosystem).
- Pre-Commit Scope: Run linters and formatters strictly on staged files (
lint-staged) to keep hook execution under 2 seconds. - Commit-Msg Validation: Enforce Conventional Commits (
feat:,fix:,chore:) viacommitlint. - Pre-Push Gate: Fast typechecking (
tsc --noEmit) and unit testing before network push. - Secret Blocking: Lightweight regex check scanning staged diffs for AWS keys, private keys, and
.envcredentials.
Output Format
- Hook Configuration Files:
lefthook.ymlor.husky/scripts +.lintstagedrc.json. - Commitlint Config:
commitlint.config.jswith allowed types and scopes. - Fast Bypass Documentation: Instructions for emergency bypass (
--no-verify).
Avoid
- Running 10-minute full end-to-end test suites on every git commit (developers will just bypass with
-n). - Formatting files across the whole repo on commit instead of staged files only.
What ships with it
2 files 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.
- 5d ago First seen · 34 lines · 39 tokens per session scan A 148a855511e4
git-hook-automation-designer is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 20d ago), licensed MIT. It adds 39 tokens to every session and 425 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
git-commit
Conventional Commits format for git commits and PR/MR titles. Type prefixes, scope rules, breaking change syntax, and commit message structure. Use when committing changes, writing commit messages, creating PR/MR titles, or formatting squash merge messages. Not for PR workflows (git-pr), CI/CD status (git-ci), or git…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
ds-commit
Smart commits — quality gates, atomic grouping, Conventional Commits formatting. Use when committing changes, grouping a working tree into atomic commits, or writing commit messages.
git-workflow-guide
Git workflow reference covering branch naming, commit message conventions, PR templates, merge strategies, and common operations — for consistent team collaboration.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.