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/zerodeng01/sublinkpro/pre-commit-checknpx skills add ZeroDeng01/sublinkPro --skill pre-commit-checkgit clone --depth 1 https://github.com/ZeroDeng01/sublinkProWhat 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.00036 | $0.02909 |
| Opus 5 | $0.00018 | $0.01455 |
| Sonnet 5 | $0.00007 | $0.00582 |
| Haiku 4.5 | $0.00004 | $0.00291 |
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 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 — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Commit Check Skill
🛑 MANDATORY VALIDATION EXECUTOR 🛑
This skill is NOT a suggestion or checklist. It is a MANDATORY EXECUTION REQUIREMENT.
Critical Rules
- Invoke this skill BEFORE any
git add,git commit, or PR creation - Execute ALL applicable validation commands
- Fix ALL failures before proceeding
- Document what was validated in commit message
- Stage changes only after validation passes
- Present to user for final verification (do NOT auto-commit)
When to Use This Skill
MANDATORY invocation before:
- Any
git addcommand - Any
git commitcommand - Any
gh pr createor PR update command - Declaring work "complete", "done", or "finished"
- User requests commit (even if they say "skip checks")
This skill is BLOCKING - you cannot proceed to commit without invoking it and ensuring all checks pass.
Skill Execution Protocol
When this skill is invoked, you MUST follow this exact sequence:
Step 1: Identify Changed Files
git status --short
git diff --name-only
git diff --cached --name-only
Categorize changes:
- Backend files (*.go)
- Frontend files (webs/*)
- Documentation files (*.md)
- Configuration files (config.yaml, .env.example, etc.)
- Mixed (multiple categories)
Step 2: Execute Backend Validation (if .go files changed)
2.1 Format Check
gofmt -l $(find . -name "*.go" -not -path "./vendor/*" -not -path "./webs/*" -not -path "./.git/*")
If output is not empty:
gofmt -w $(find . -name "*.go" -not -path "./vendor/*" -not -path "./webs/*" -not -path "./.git/*")
Verify:
gofmt -l $(find . -name "*.go" -not -path "./vendor/*" -not -path "./webs/*" -not -path "./.git/*")
BLOCKING: Must return empty output (all files formatted).
2.2 Lint Check
golangci-lint run
BLOCKING: Must exit with status 0.
If fails: Read the errors, fix them, and re-run. Do NOT proceed until clean.
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 · 404 lines · 36 tokens per session scan A 0337af2d5ccf
pre-commit-check is a skill published in the GitHub repository ZeroDeng01/sublinkPro (1,599 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 2,909 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…