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 atman-33/workhub --skill commit-changesgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/commit-changes)<a href="https://agentmods.dev/skills/atman-33/workhub/commit-changes"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/commit-changes/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/atman-33/workhub/commit-changes"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/commit-changes.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.00036 | $0.00361 |
| Opus 5.5 | $0.00014 | $0.00144 |
| Sonnet 5.5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
commit-changes 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 the current changes with a Conventional Commits message.
Steps
-
Assess the working tree. Run
git status --shortandgit diff(orgit diff --stagedif changes are already staged) to see what changed and why.- Completion criterion: the changed files and their purpose are known.
-
Stage changes. If nothing is staged, run
git add ..- Completion criterion: at least one change is staged.
-
Draft the message. Pick a Conventional Commits prefix based on the diff:
feat— new featurefix— bug fixdocs— documentation onlystyle— formatting, missing semicolons, etc.refactor— code change that neither fixes a bug nor adds a featuretest— adding or correcting testschore— build process or auxiliary tool/library changes Then write a short imperative description in<type>: <description>format. Use English unless the user requested another language.- Completion criterion: the message follows the format and matches the change.
-
Commit. Run
git commit -m "<message>".- Completion criterion: the commit succeeds and its hash is shown.
Failure modes
- No changes to commit: stop and report.
gitnot in a repository: stop and report.- Multiple unrelated changes: consider splitting into multiple commits and ask the user.
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 Changed · -8 tokens per session 505e7505cdd7
- 1mo ago First seen · 34 lines · 44 tokens per session scan A a804bdebd0cb
commit-changes is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 361 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-08-31.
Other skills, from other repositories
git-commit
Generate well-formatted git commit messages following conventional commit standards.
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.
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
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"…
commit
Changelog and commit — lightweight motion for day-to-day plugin dev work in the monorepo. One commit per plugin scope; CHANGELOG and staging routed by detected slug. Trigger when the user says "commit", "commit this", "save this", "wrap this up", "let's commit", or finishes a change and wants to capture it. NOT for…