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/outlinedriven/outline-driven-development/commit-economynpx skills add OutlineDriven/outline-driven-development --skill commit-economygit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/commit-economy)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/commit-economy"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/commit-economy.svg" alt="Measured on agentmods" 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.00062 | $0.01090 |
| Opus 5 | $0.00031 | $0.00545 |
| Sonnet 5 | $0.00012 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
commit-economy 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- commit-economy — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit economy
Contract
| Field | Bound contract |
|---|---|
| Trigger | User asks to clean up a finished commit's message, or a commit message needs handoff-ready form. |
| Authority | Rewrite only VCS-tracked commit messages. Show the exact commit set before mutation. Use the original refs and reflog as recovery. Never create or suggest a new commit. |
| Side effect | Rewrites commit messages only; the tree stays byte-identical; each rewritten commit is re-signed with its dates preserved by position. Local history only. |
| Done | git diff old..new is empty; each rewritten commit is signed with the intended dates; git log alone carries the handoff with the diff hidden. |
Inputs
- The target commit or range:
HEADor a short unpushed range (HEAD~N..HEAD). Optional; default isHEAD. - The intended message text for each target commit. Must be supplied by the user or derived from the existing message; never invented.
- Confirmation when any target commit is already pushed to a shared remote. Required before proceeding; otherwise stop.
Procedure
- Determine the exact target set:
HEAD, orHEAD~N..HEADfor a short unpushed range. List the commits withgit log --format='%H %an <%ae> %ad %cn <%ce> %cd' <range>so the set and per-position author/committer dates are visible. Done when: the exact commit set is listed with per-position dates. - Confirm that none of the target commits are pushed to a shared remote (
git branch -r --contains <sha>). If any is pushed, stop and require explicit user confirmation before continuing. Pushed history is otherwise untouched. Done when: all targets are confirmed unpushed or explicit confirmation is received for pushed commits. - Record each target commit's original tree SHA (
git rev-parse <sha>^{tree}) and original author and committer dates, keyed by position in the range. Re-signing must preserve these dates by position. Done when: every target's tree SHA and dates are recorded by position. - Never create or suggest a new commit. Only rewrite the message of existing commits in the target set. Done when: the no-new-commit constraint is confirmed before mutation.
- Rewrite each target commit's message to handoff-ready form. When the diff is hidden, the message must let
git logalone carry the handoff by stating what changed and why without relying on the diff. Usegit rebasewithGIT_SEQUENCE_EDITORandgit commit --amend/--reedit-message, orgit filter-repo --message-callback, scoped to the exact range. Done when: every target commit's message is rewritten to handoff-ready form. - Re-sign each rewritten commit while preserving its original author and committer dates by position. Set
GIT_AUTHOR_DATEandGIT_COMMITTER_DATEto the recorded per-position values during each amend; do not let them slip to now. Done when: every rewritten commit is re-signed with its original dates by position. - Verify the done predicate: run
git diff <old>..<new>and confirm it is empty (tree byte-identical); confirm each rewritten commit's author and committer dates match the recorded per-position values; confirmgit logfor the range carries the handoff withgit show/diff hidden. Done when: the diff is empty, dates match by position, and the log carries the handoff.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 42 lines · 62 tokens per session scan A 02da58476502
commit-economy is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed today), licensed Apache-2.0. It adds 62 tokens to every session and 1,090 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.
commit-push
Use when asked to commit and push to a feature branch off the default branch, with no pull request. Not for a PR: use commit-push-pr. Not for the checked-out branch: use commit-push-current.
commit-push-current
Use when a human explicitly asks to commit and push to the checked-out branch, with no branch creation and no pull request. Not for the default branch by name: use commit-push-main.
setup-pre-commit
Use when installing or repairing a repo-local pre-commit hook from the project gates, or when a repo needs package-manager-native commit-time checks. Not for remote or irreversible changes.