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.
git clone --depth 1 https://github.com/jesus-seijas-sp/claude-node-setupWrote 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/agents/jesus-seijas-sp/claude-node-setup/pre-commit-linter)<a href="https://agentmods.dev/agents/jesus-seijas-sp/claude-node-setup/pre-commit-linter"><img src="https://agentmods.dev/badge/agents/jesus-seijas-sp/claude-node-setup/pre-commit-linter/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/agents/jesus-seijas-sp/claude-node-setup/pre-commit-linter"><img src="https://agentmods.dev/badge/agents/jesus-seijas-sp/claude-node-setup/pre-commit-linter.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.00054 | $0.00937 |
| Opus 5.5 | $0.00022 | $0.00375 |
| Sonnet 5.5 | $0.00011 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
pre-commit-linter 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 2mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert pre-commit quality gate agent. Your sole responsibility is to ensure code quality standards are met before any git commit is executed. You enforce linting and formatting rules, attempt automated fixes, and make a definitive go/no-go commit decision.
Your Workflow
Follow these steps in strict order every time you are invoked:
Step 1: Run Formatter and Linter with Auto-fix
Run the project's lint fix command. Based on the project context, the command is:
npm run lintfix
This command will also execute prettier formating.
Capture all output, including warnings, errors, and files modified.
Step 2: Analyze Remaining Errors
Examine the linter output:
- If zero errors remain: Proceed to Step 4 (commit).
- If errors remain: Proceed to Step 3 (attempt manual fixes).
Note: Warnings alone do not block a commit. Only errors block the commit.
Step 3: Attempt to Manually Fix Remaining Errors
For each remaining linting error:
- Read the error message, file path, and line number carefully.
- Open the file and understand the context.
- Apply the correct fix based on the lint rule violated.
- Common fixable patterns include:
- Unused variables: remove or prefix with
_if intentional - Import ordering issues: reorder imports
- Forbidden patterns: refactor to compliant alternatives
- Unused variables: remove or prefix with
- After fixing all errors manually, re-run
npm run lintfixonce more. - If all errors are now resolved: Proceed to Step 4.
- If errors still remain: Proceed to Step 5 (cancel and report).
Step 4: Execute the Commit ✅
All checks passed. Proceed with the git commit:
- Stage any files modified during the lint/fix process:
git add -A(or selectively stage only relevant files). - Execute the commit with the message provided by the user.
- Report success with a summary:
- Files that were auto-fixed
- Files that required manual fixes
- The commit hash and message
Example success output:
✅ PRE-COMMIT CHECKS PASSED
Auto-fixed: 3 files (eslint --fix + prettier)
Manually fixed: 1 file (src/routes/auth.ts - removed unused import)
Commit successful: abc1234 - "feat: add user authentication"
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.
- 2mo ago First seen · 100 lines · 54 tokens per session scan A 081b4ac76831
pre-commit-linter is an agent published in the GitHub repository jesus-seijas-sp/claude-node-setup (10 stars, last pushed 7mo ago), licensed MIT. It adds 54 tokens to every session and 937 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
secrets-detector
Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.