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/laurigates/claude-plugins/configure-pre-commitnpx skills add laurigates/claude-plugins --skill configure-pre-commitgit clone --depth 1 https://github.com/laurigates/claude-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/laurigates/claude-plugins/configure-pre-commit)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-pre-commit"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-pre-commit.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.01730 |
| Opus 5 | $0.00016 | $0.00865 |
| Sonnet 5 | $0.00007 | $0.00346 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
configure-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 today.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:pre-commit
Check and configure pre-commit hooks against project standards.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up or validating pre-commit hooks | Project doesn't use pre-commit framework (use git hooks directly) |
| Checking compliance with project standards | Just running hooks manually (use pre-commit run command) |
| Installing project-type-specific hooks | Hooks are already properly configured |
| Migrating to pre-commit framework | Simple project with no quality checks needed |
| Updating hook configurations for detected tools | Need to disable pre-commit entirely |
Context
- Pre-commit config: !
find . -maxdepth 1 -name \'.pre-commit-config.yaml\' - Project standards: !
find . -maxdepth 1 -name \'.project-standards.yaml\' - Project type in standards: !
find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^project_type:" {} + - Has terraform: !
find . -maxdepth 2 \( -name '*.tf' -o -type d -name 'terraform' \) -print -quit - Has helm: !
find . -maxdepth 2 -type d -name 'helm' -print -quit - Has package.json: !
find . -maxdepth 1 -name \'package.json\' - Has pyproject.toml: !
find . -maxdepth 1 -name \'pyproject.toml\'
Parameters
Parse from $ARGUMENTS:
--check-only: Report status without offering fixes--fix: Apply all fixes automatically without prompting--type <type>: Override project type detection (frontend,infrastructure,python)
Execution
Execute this pre-commit compliance check:
Step 1: Detect project type
- Read
.project-standards.yamlforproject_typefield if it exists - If not found, auto-detect:
- infrastructure: Has
terraform/,helm/,argocd/, or*.tffiles - frontend: Has
package.jsonwith vue/react dependencies - python: Has
pyproject.tomlorrequirements.txt
- infrastructure: Has
- Apply
--typeflag override if provided
Step 2: Check configuration file
What ships with it
1 file 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.
- today First seen · 167 lines · 33 tokens per session scan A 4360792622be
configure-pre-commit is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,730 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
plan
Produce structured implementation plans with goal, approach, test strategy, blast-radius assessment, parallelism analysis, and a user approval gate before any code is written. Persisting PLAN.md for fresh-session handoff. Use when: 'plan this', 'architect this', 'how should we implement', 'implementation plan', 'write…
extract-ssot
Deduplicate repeated markdown content, rule files, skill bodies, ADRs, docs, into a single named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept appears (or is reworded) across files: 'DRY this prose', 'extract a shared rule', 'single source of…
map-corpus
Map a multi-resource documentation corpus into a verified, classified, triaged slice BEFORE any digesting: bounded discovery (llms.txt + sitemap), a user-approved link map classifying every discovered URL, deterministic node manifests over immutable snapshots, and a per-node relevance inventory whose evidence a script…
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.