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 skills add jscraik/Agent-Skills --skill prek-progit clone --depth 1 https://github.com/jscraik/Agent-SkillsWrote 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/jscraik/agent-skills/prek-pro)<a href="https://agentmods.dev/skills/jscraik/agent-skills/prek-pro"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/prek-pro/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/skills/jscraik/agent-skills/prek-pro"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/prek-pro.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.00032 | $0.01312 |
| Opus 5.5 | $0.00013 | $0.00525 |
| Sonnet 5.5 | $0.00006 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
prek-pro 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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prek Pro
Philosophy
- Keep the skill focused on the decision and workflow the user actually requested.
- Preserve important context through progressive disclosure instead of trimming it away.
- Prefer repo-local contracts, wrappers, and validation before generic advice.
When To Use
- The user is editing or debugging prek.toml.
- A project needs prek shims, hook installation, or validation.
- A pre-commit setup is being migrated to prek.
- A commit hook reports unstaged changes, stashes to a prek patch, restores a patch unexpectedly, or leaves staged/unstaged state different from the state observed before commit.
Avoid
- Generic linting with no prek hook surface.
- Changing hook behavior without running the repo hook validation.
- Treating prek and pre-commit as identical when their config differs.
Inputs
- prek.toml path
- hook failure output
- runtime manager
- migration source
- validation command
Outputs
- config guidance or patch
- shim/install notes
- failure diagnosis
- validation evidence
- remaining blockers
- Schema-bound outputs include schema_version.
Workflow
- Start with 2-3 focused surfaces before expanding scope.
- Read the existing hook config and repo instructions first.
- Identify whether the task is setup, migration, validation, or debugging.
- Use docs-backed prek syntax and project-local wrappers.
- Keep hook changes scoped to the failing behavior.
- Run the hook or validation command that proves the fix.
- For commit-hook stash failures, inspect
git status --short --branch, staged and unstaged file lists, and the reported~/.cache/prek/patches/*.patchbefore applying, discarding, or retrying anything. - Treat a prek patch as evidence, not as intended work, until its hunks match the user-authorized change set.
- Prefer a fully staged, clean working tree before running commit hooks that may
rewrite generated files. Avoid
git commit --only, path-limited commits, or partial index commits when repo hooks can sync projections, format docs, or restore prek patches. - If prek mutates the worktree during commit, stop before retrying unless the mutation is clearly hook-generated and inside the authorized change scope.
What ships with it
3 files 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.
- 1mo ago First seen · 132 lines · 32 tokens per session scan A 8402a01d6e7d
prek-pro is a skill published in the GitHub repository jscraik/Agent-Skills (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 1,312 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
sk-hashline-protocol
Enforces hash-anchored line verification to prevent stale-line edits during file mutations. Use when any agent performs file mutations in a worktree — mandates that read lines carry content-identifier hashes and that those hashes are verified before an edit is committed.
remote-fix
Remote fix workflow. Receives a diagnostic (from Cowork scheduled task, manual observation, or user report), investigates the issue, fixes it, and creates a PR. Designed for quick fixes triggered remotely via Channels (Discord/Telegram). Use when the user says "fix this", "handle this diagnostic", "the scheduled task…
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.