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 jrjsmrtn/project-orchestration-skills --skill setup-pre-commitgit clone --depth 1 https://github.com/jrjsmrtn/project-orchestration-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/jrjsmrtn/project-orchestration-skills/setup-pre-commit)<a href="https://agentmods.dev/skills/jrjsmrtn/project-orchestration-skills/setup-pre-commit"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/setup-pre-commit.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.1 | $0.00062 | $0.00475 |
| Opus 5 | $0.00031 | $0.00237 |
| Sonnet 5 | $0.00012 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
setup-pre-commit 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 7d 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.
What it actually says
Setup Pre-commit Hooks (deprecated)
This skill was renamed to setup-git-hooks in 0.1.29. Invoke that instead.
Do not follow any procedure from this file. It retains no content — it exists solely so that an invocation of the old name yields a pointer rather than silence.
Why it was renamed
The old name was wrong on two axes at once:
- It named one of the two stages. The skill's thesis is the two-stage split — fast checks on commit, thorough checks on push. The pre-push stage is roughly a third of the content and carries the checks that catch the expensive defects.
- It named one of the two supported hook managers. The skill documents both
pre-commitandlefthook; its "Install Hook Framework" step mentionslefthookmore often thanpre-commit, and roughly half the skill (.editorconfig, secret-detection architecture,.gitignorehardening, multi-remote protection) involves no hook manager at all.
The practical effect was that maintainers on Elixir, Go or Rust projects read "pre-commit", correctly inferred "that is the Python hook framework", and never reached the content that had nothing to do with it.
See workspace ADR-0013.
Migration
Replace any invocation of setup-pre-commit with setup-git-hooks. There is no behavioural change —
same workflow, same steps, same outputs.
Removal
This stub will be removed at 0.2.0. It exists only for the deprecation window, because the skill, plugin and marketplace manifests provide no rename, alias or redirect mechanism — content-level deprecation is the only graceful path the format offers.
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.
- 7d ago First seen · 45 lines · 62 tokens per session scan A 0ff666d686e0
setup-pre-commit is a skill published in the GitHub repository jrjsmrtn/project-orchestration-skills (15 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 475 once invoked, about $0.0003 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
maestro-improve
Turn filed lessons into the smallest doctrine edit. Use when a Lead assigns improvement work for one target: group pending lessons, make one evidence-linked commit per target, return it for independent challenge, and process each accepted or rejected lesson without deleting history.
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
levelup-publish
Compile accepted Context Directive Records (CDRs) into team-ai-directives artifacts and create a draft PR. Builds context modules, evals goldensets, and/or skills based on CDR context types.
git-commit-push-pr
Commit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", "commit push PR", or wants to go from working changes to an open pull request in one step. Also use when the user says "update the PR…
git-commit
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit…
git-commit-validator
MUST be used for ANY git workflow that involves committing code. This includes explicit commit requests AND implicit ones like 'ship it', 'wrap it up', or finishing implementation work. Handles staging, message generation, validation, and commit execution with conventional commit format.