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 nirelbaz/promptpit --skill commitgit clone --depth 1 https://github.com/nirelbaz/promptpitWrote 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/nirelbaz/promptpit/commit)<a href="https://agentmods.dev/skills/nirelbaz/promptpit/commit"><img src="https://agentmods.dev/badge/skills/nirelbaz/promptpit/commit/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/nirelbaz/promptpit/commit"><img src="https://agentmods.dev/badge/skills/nirelbaz/promptpit/commit.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.00043 | $0.00298 |
| Opus 5.5 | $0.00017 | $0.00119 |
| Sonnet 5.5 | $0.00009 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
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 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.
What it actually says
Commit
Write a commit message for the staged changes.
Process
- Run
git diff --cachedto see what's staged - If nothing is staged, run
git statusand tell the user what's available to stage - Analyze the changes and write a commit message
Commit message format
Use conventional commits:
type(scope): short description
Longer explanation of why this change was made,
if the why isn't obvious from the description.
Types: feat, fix, refactor, test, docs, chore, perf
Scope: the area of code affected (optional, use when it adds clarity)
Rules
- The short description should be under 72 characters
- Write in imperative mood: "add feature" not "added feature"
- The description says WHAT changed. The body says WHY.
- If the change is trivial (typo fix, formatting), skip the body
- If the change touches multiple areas, consider whether it should be multiple commits
- Never include file lists in the message. The diff already shows exactly what changed, and manual lists go stale if the commit is amended.
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 · 40 lines · 43 tokens per session scan A bf8aad24c169
commit is a skill published in the GitHub repository nirelbaz/promptpit (6 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 298 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 skills, from other repositories
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
knowledge-shell-process-and-worktree
Shell and Git worktree support for running commands, managing long-lived processes, and giving sessions isolated working directories. A Git worktree is a separate checkout linked to the same repository.
commit
Create well-formatted commits with conventional commit messages and emoji.
git-notes
Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.
cf-commit
Smart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
datalad
Retrieve, version, and publish scientific datasets with DataLad and git-annex, and capture computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink or a…