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 acolomba/pi-claude-marketplace --skill committinggit clone --depth 1 https://github.com/acolomba/pi-claude-marketplaceWrote 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/acolomba/pi-claude-marketplace/committing)<a href="https://agentmods.dev/skills/acolomba/pi-claude-marketplace/committing"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/committing/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/acolomba/pi-claude-marketplace/committing"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/committing.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.00045 | $0.00481 |
| Opus 5.5 | $0.00018 | $0.00192 |
| Sonnet 5.5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
committing 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
Committing
Which checks a task or gate needs is in .agents/skills/local-verification/SKILL.md.
Messages
Commit messages and PR titles follow the Conventional Commits specification. Titles have 5 to 72 characters; body lines have at most 80. Messages name no GSD milestone, phase, plan, or wave, including in the scope: write test(orders): ..., not test(03-01): ..., whatever a GSD template suggests.
Procedure
While editing, run owner tests or one pair's direct coverage. Before committing, run SKIP=npm-check pre-commit run --files <changed files> to apply fixers and linters. It takes seconds. A linter warning fails it too, because yamllint runs with --strict. Restage fixes and repeat until clean. To run them on every file, as the CI Lint workflow does, use SKIP=npm-check pre-commit run --all-files.
Then run git commit in the foreground with the longest tool timeout available. Never background it and poll with sleep/grep loops. If a run can outlast the tool's foreground limit, background it once and wait for the completion notification. The commit hook runs the npm checks; do not run ESLint, type checking, or tests immediately beforehand. A failed hook means no commit happened: fix, restage, and commit again, without --amend (it would alter the previous commit) or --no-verify.
During git commit, pre-commit stashes unstaged edits. It does not move untracked files, so stage or remove untracked build inputs before you commit. The pre-commit tool passes no deleted file to a hook, and it applies its top-level exclude first. So the hook skips a commit that only deletes build inputs or only changes files under test/domain/fixtures/hash-stability/. Run npm run check yourself before such a commit.
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 Changed e7c64ae9d81c
- 15d ago First seen · 21 lines · 45 tokens per session scan A f12d99a767f2
committing is a skill published in the GitHub repository acolomba/pi-claude-marketplace (28 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 481 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-10-15.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…