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 agentmods add skills/jakubsuplicki/codument/commit-worknpx skills add jakubsuplicki/codument --skill commit-workgit clone --depth 1 https://github.com/jakubsuplicki/codumentWhat 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 | $0.00021 | $0.00814 |
| Opus 5 | $0.00010 | $0.00407 |
| Sonnet 5 | $0.00004 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00081 |
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 2d 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 the user has approved/deferred every review finding and all approved fixes are resolved.
Workflow
- Check the active plan step is complete. If it was the final step, confirm the
## 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 --short. - Review the diff and avoid staging unrelated user changes.
- Run the relevant verification commands.
- Run
codument review --strict— it must pass. It exits nonzero while the step left a new source unmapped or a mapped doc stale; materialize the file(s) (codument map materialize <file>) and update the stale doc(s), then re-run until clean. Do not commit while it is red. - Stage only files belonging to the completed step.
- Commit with a conventional commit prefix:
feat:fix:docs:test:refactor:chore:
- If that was the plan's last step, run
codument doctor --strictonce and report what it says. It 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:reviewanswers "is this change in sync",doctoranswers "is the knowledge base still worth reading", and a field run made 37 review-family calls across five commits without ever learning its own health surface stood at 140 findings, including one on a doc that session had just edited. Once per plan, not once per step. - Continue directly to
work-stepfor the next unchecked step, or report completion if none remain. In gated mode, stop after the commit and offer the next-step gate instead:
Step N is reviewed and committed. Next options:
1. Start the next unchecked plan step with /work-step
2. Review the plan before continuing
3. Compact context before continuing
4. Pause here
- If the user chooses compact context, use the active agent's native context-compaction command when one is available. If no native command is available, provide a concise restart note grounded in
AGENTS.md, the active plan doc,docs/.registry.json, andgit status, then pause.
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.
- 2d ago First seen · 49 lines · 21 tokens per session scan A cca1c41bebc9
commit-work is a skill published in the GitHub repository jakubsuplicki/codument (47 stars, last pushed 12d ago), licensed Apache-2.0. It adds 21 tokens to every session and 814 once invoked, about $0.0001 per session on Opus 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
flow-next-work
Execute a flow-next spec or task end-to-end with worker subagents, gates, and commits. Use when asked to work on, implement, or execute fn-N.
trellis-finish-work
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
kn-commit
Use when committing code changes with proper conventional commit format and verification.
campaign-commit
Choose the correct commit command in a campaign workspace. Use when you are about to commit and need to select camp commit, camp p commit, fest commit, or intentional root pointer sync via camp refs-sync.
doc-sync
Incremental skill updater that maps git diffs to affected skills and optionally auto-syncs via a post-commit hook.
submit
Complete submission workflow - quality checks, commit, PR creation, changelog generation, and final push. Use after finishing implementation work.