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/kissrosecicd-hub/agents-evolution/pre-commit-setupnpx skills add kissrosecicd-hub/agents-evolution --skill pre-commit-setupgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWhat 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.00000 | $0.01134 |
| Opus 5 | $0.00000 | $0.00567 |
| Sonnet 5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
pre-commit-setup 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-commit & Code Quality Setup
Триггеры: "pre-commit", "настроить линтинг", "code quality gate", "lizard", "cyclomatic complexity", "настроить linter", "pre-commit hook", "статический анализ", "настроить проверку перед commit", "check before commit", "автопроверка кода", "настроить code quality"
Контекст
Настройка pre-commit хуков для проверки кода перед commit. Включает linter, formatter, complexity check.
Обязательный инструмент: Lizard
Анализатор cyclomatic complexity для ВСЕХ языков.
pip install lizard # или uv pip install lizard
lizard -l 15 -n 300 -a 10 <dir>
Ориентиры: complexity ≤ 15, NLOC ≤ 300, параметры ≤ 10.
Инструменты по языкам
| Язык | Линтер | Форматер | Анализатор |
|---|---|---|---|
| Python | ruff | ruff format | mypy, lizard |
| TypeScript | eslint, biome | biome, prettier | tsc --noEmit |
| JavaScript | eslint | prettier | lizard |
| Go | golangci-lint | gofmt | go vet |
| Rust | clippy | rustfmt | cargo check |
| C/C++ | clang-tidy | clang-format | cppcheck |
| Java | checkstyle | spotless | pmd |
Примеры pre-commit-config.yaml
Python
repos:
- repo: local
hooks:
- id: ruff-check
name: ruff check
entry: uv run ruff check --force-exclude
language: system
types: [python]
- id: ruff-format
name: ruff format
entry: uv run ruff format --check
language: system
types: [python]
- id: lizard
name: lizard complexity
entry: uv run lizard -l 15 -n 300 -a 10 .
language: system
types: [python]
TypeScript/JavaScript
repos:
- repo: local
hooks:
- id: eslint
name: eslint
entry: npx eslint
language: system
types: [ts, tsx, javascript]
- id: biome
name: biome format
entry: npx @biomejs/biome format --write
language: system
types: [ts, tsx, javascript]
- id: tsc
name: type check
entry: npx tsc --noEmit
language: system
types: [ts, tsx]
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 · 144 lines · 0 tokens per session scan A 4d8db53c5b09
pre-commit-setup is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,134 tokens. 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…