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 commands/thebeardedbearsas/claude-craft/pre-commit-checkgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/commands/thebeardedbearsas/claude-craft/pre-commit-check)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/pre-commit-check"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/pre-commit-check.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.00006 | $0.01422 |
| Opus 5 | $0.00003 | $0.00711 |
| Sonnet 5 | $0.00001 | $0.00284 |
| Haiku 4.5 | $0.00001 | $0.00142 |
Grade A, and why
pre-commit-check 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 4d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vérification Pre-Commit
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
Arguments
$ARGUMENTS
Options :
--fix: Corriger automatiquement les problèmes corrigeables--staged: Vérifier uniquement les fichiers stagés
MISSION
Étape 1 : Identifier les Fichiers Modifiés
# Fichiers stagés
git diff --cached --name-only
# Fichiers modifiés (non stagés)
git diff --name-only
Étape 2 : Détecter la Technologie par Fichier
| Extension | Technologie | Outils |
|---|---|---|
.php |
PHP/Symfony | php-cs-fixer, phpstan |
.dart |
Flutter | dart format, dart analyze |
.py |
Python | ruff, mypy |
.ts, .tsx |
React/RN | eslint, prettier |
.js, .jsx |
React/RN | eslint, prettier |
Étape 3 : Exécuter les Vérifications
Pour les fichiers PHP
# Formatage
docker compose exec php vendor/bin/php-cs-fixer fix --dry-run --diff [fichiers]
# Analyse statique
docker compose exec php vendor/bin/phpstan analyse [fichiers]
# Syntaxe Twig (si modifiés)
docker compose exec php php bin/console lint:twig templates/
# Container Symfony
docker compose exec php php bin/console lint:container
Pour les fichiers Dart/Flutter
# Formatage
docker run --rm -v $(pwd):/app -w /app dart dart format --set-exit-if-changed [fichiers]
# Analyse
docker run --rm -v $(pwd):/app -w /app dart dart analyze [fichiers]
# Tests affectés
docker run --rm -v $(pwd):/app -w /app dart flutter test --coverage
Pour les fichiers Python
# Linting + formatage
docker compose exec app ruff check [fichiers]
docker compose exec app ruff format --check [fichiers]
# Types
docker compose exec app mypy [fichiers]
Pour les fichiers JS/TS
# Linting
docker compose exec node npx eslint [fichiers]
# Formatage
docker compose exec node npx prettier --check [fichiers]
# Types (si TypeScript)
docker compose exec node npx tsc --noEmit
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.
- 4d ago First seen · 206 lines · 6 tokens per session scan A c1affcb7a420
pre-commit-check is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 1,422 once invoked, about $0.0000 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.