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 agentmods add skills/andrewsrigom/agent-skills/setup-pre-commitnpx skills add andrewsrigom/agent-skills --skill setup-pre-commitgit clone --depth 1 https://github.com/andrewsrigom/agent-skillsWhat 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 | $0.00046 | $0.00531 |
| Opus 5 | $0.00023 | $0.00266 |
| Sonnet 5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
setup-pre-commit 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 2d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Pre-Commit
Use this skill when the user wants commit-time checks without overloading the hook.
Scope
- Husky setup
- lint-staged configuration
- Prettier or existing formatter integration
- package-manager-aware hook commands
- choosing what belongs in pre-commit versus CI
Default path
- Detect the package manager and current scripts.
- Install the minimum hook dependencies.
- Initialize Husky if the repo does not already use it.
- Configure
lint-stagedfor staged-file formatting or linting. - Keep the pre-commit hook fast:
- staged formatting or linting first
- lightweight checks second
- heavy suites in CI unless the repo explicitly wants them locally
- Verify the hook against the current scripts instead of inventing missing commands.
When to deviate
- Keep the hook even smaller when the repo already struggles with slow local tooling.
- Add more checks only if the repo already runs them reliably and the team explicitly wants them before commit.
- Skip formatter or lint changes if the repo already has a working hook stack that only needs a small fix.
Guardrails
- Do not add
typecheckortestto the hook if the repo does not already support them cleanly. - Prefer staged-file checks over whole-repo checks in pre-commit.
- Keep the hook deterministic and package-manager-aware.
- Do not introduce a formatter config if the repo already has one.
Avoid
- turning pre-commit into a slow mini-CI pipeline
- inventing scripts the repo does not actually have
- running whole-repo checks when staged-file checks are enough
- overwriting an existing formatter setup without reason
Verification checklist
- the package manager and current scripts were detected first
- hook commands are fast enough for normal commit flow
- checks operate on staged files where possible
- CI-only work stays out of pre-commit unless explicitly desired
- the hook matches the repo's real tooling, not imagined tooling
Output Shape
When answering with this skill, prefer:
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.
- 2d ago First seen · 70 lines · 46 tokens per session scan A ed5932fed5d3
setup-pre-commit is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 531 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
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…