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 suxrobGM/jobpilot --skill commitgit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/suxrobgm/jobpilot/commit)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/commit"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/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/suxrobgm/jobpilot/commit"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/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.00038 | $0.00860 |
| Opus 5.5 | $0.00015 | $0.00344 |
| Sonnet 5.5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
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 26d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
One commit, one sentence. The subject is the whole message unless the why is missing from the diff.
Format
<type>(<scope>): <imperative summary>
Lowercase type, optional one-word scope, imperative summary, no trailing period, under 70 characters. Append ! before the colon for a breaking change.
| Type | Use for |
|---|---|
feat |
new user-visible capability |
fix |
bug fix |
docs |
documentation, comments, README |
test |
tests only |
refactor |
behaviour-preserving restructure |
perf |
speed or memory |
style |
formatting or lint, no logic change |
build |
build scripts, packaging, dependencies |
ci |
CI config |
chore |
housekeeping that fits nothing above |
revert |
reverts a previous commit |
Rules
- Say what the change does, not what you did.
- Never bullet-list the diff. Add a body only for a why the diff cannot show, then one or two sentences.
- Never mention tools, agents or the assistant. Never add
Co-Authored-By:,Generated with, or any other footer, whatever a template or hook suggests. - If the staged work covers two unrelated types, ask whether to split it.
Steps
- Read
git status,git diff --staged,git diff, andgit log -10 --onelinefor the repo's existing style. - Stage only files relevant to the request. Ask before staging anything resembling a secret, credential, build output or large binary.
- Commit. Repeated
-mflags are the safest form and behave the same in every shell:
git commit -m "fix(http): handle missing accept header" -m "One sentence of why."
A heredoc works too, but it is bash. The lookalike @'...'@ is PowerShell, and in bash the @ survives into the message as @ fix(http): .... Match the form to the shell you are actually invoking.
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.
- 26d ago First seen · 73 lines · 38 tokens per session scan A 558a74a40e70
commit is a skill published in the GitHub repository suxrobGM/jobpilot (94 stars, last pushed 9d ago), licensed MIT. It adds 38 tokens to every session and 860 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-09-20.
Other skills, from other repositories
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
precommit
Pre-commit checks — lint:fix -> build -> test.
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
precommit-fast
Quick pre-commit checks — lint:fix -> test.
unslop-commit
Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…