Borrowing it
Nothing to install: this file belongs to jakubsuplicki/codument. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jakubsuplicki/codument/main/.agents/skills/commit-work/SKILL.mdgit clone --depth 1 https://github.com/jakubsuplicki/codumentWrote 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/jakubsuplicki/codument/commit-work)<a href="https://agentmods.dev/skills/jakubsuplicki/codument/commit-work"><img src="https://agentmods.dev/badge/skills/jakubsuplicki/codument/commit-work/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/jakubsuplicki/codument/commit-work"><img src="https://agentmods.dev/badge/skills/jakubsuplicki/codument/commit-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.00913 |
| Opus 5.5 | $0.00007 | $0.00365 |
| Sonnet 5.5 | $0.00003 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
commit-work 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 23d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Work
Use this after review-work is clean, or after safe contracted fixes and user-approved fixes are
resolved and the user has explicitly deferred any remaining finding.
Workflow
-
Check the active plan step is complete, using its recovery copy at
.codument/pending-plans/<repo-relative-plan-path>after final-step compaction. For the final step, confirm the original doc's## Delivery Planblock has been compacted out (plan-with-docs → Compaction on ship) — a shipped feature doc must not commit with a stale delivery checklist still in it. -
Check that
review-workis clean, or that every finding was fixed or explicitly deferred by the user. -
Check
git status --shortandgit diff --cached. -
Confirm
codument work status --jsonshows the reviewed step ready and the already-staged, verified boundary unchanged; do not stage here. If it changed, return to review and verification. Respect an explicit no-commit request: leave the step ready and stop. -
Commit that boundary with a conventional commit prefix. The managed pre-commit hook runs
codument verify; when the staged boundary, approval, review policy and review evidence remain current, it reuses the exact receipt instead of repeating the review:feat:fix:docs:test:refactor:chore:
A routine hook failure returns to diagnosis, correction and exact staged review within the approved contract. Never bypass the hook or commit a red boundary; pause only if repair needs an unapproved decision, external input or genuinely irreversible action, or the user has requested a pause.
-
If that was the plan's last step, remove only this plan's recovery copy after confirming the commit succeeded, then run
codument doctor --strictonce and report what it says. If interrupted before cleanup, reconcile the copy with the committed boundary before resuming; a leftover copy does not authorize repeating completed work. Doctor reports; it does not gate — a plan must not be blocked by an adopting repo's pre-existing debt. This is the only moment the loop looks at repo-wide health: stagedverifyanswers whether this change is ready,doctoranswers whether the knowledge base is still worth reading. Once per plan, not once per step. -
After the successful commit, run
codument work finishto reconcile delivery, then readcodument steps --plan <active-plan> --jsonif the Delivery Plan remains. Name the next step and continue towork-stepunless gated or single-step mode requires stopping. Completed local state must agree with committed delivery; a missing checklist alone is not completion. In gated mode, fill the next-step gate from that readback:
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.
- 23d ago Changed · +3 lines d31f8d566331
- 1mo ago Changed · -3 lines · -4 tokens per session 15e615877ab0
- 1mo ago First seen · 49 lines · 21 tokens per session scan A cca1c41bebc9
commit-work is a skill published in the GitHub repository jakubsuplicki/codument (48 stars, last pushed 23d ago), licensed Apache-2.0. It adds 17 tokens to every session and 913 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-30.
Other skills, from other repositories
do
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended or in lanes, then close. Use for "implement", "next task".
kn-commit
Use when committing code changes with proper conventional commit format and verification.
committing
Creates quality git commits with conventional commit format. Use when asked to commit changes or create a commit message.
sc-diff-report
Incremental security scan for changed files only — optimized for PR and commit-level reviews.
commit-conventions
Enforces conventional commit format with atomic changes and co-author attribution. Used when committing code changes to maintain consistent git history.
tdd
Enforces red-green-refactor TDD cycle with atomic commits per phase. Used when implementing features, fixing bugs, or when tests should drive the design.