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 orin-dx/agent-plugins --skill commitgit clone --depth 1 https://github.com/orin-dx/agent-pluginsWrote 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/orin-dx/agent-plugins/commit)<a href="https://agentmods.dev/skills/orin-dx/agent-plugins/commit"><img src="https://agentmods.dev/badge/skills/orin-dx/agent-plugins/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/orin-dx/agent-plugins/commit"><img src="https://agentmods.dev/badge/skills/orin-dx/agent-plugins/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.00033 | $0.00296 |
| Opus 5.5 | $0.00013 | $0.00118 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 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
State material concerns, evidence, consequence, and confidence directly. Do not soften blockers, manufacture praise, or claim certainty beyond the evidence.
Commit verified work
Inspect the staged diff, staged file list, and recent commit history before drafting anything. Do not infer scope from unstaged work or a task description when the index says otherwise.
Workflow
- Confirm that the index contains the intended files and identify the smallest coherent change represented by it.
- Read
shared/references/delivery/commits.mdfor type, scope, and voice rules. - Draft a conventional commit subject and body that explains why the change exists. Let the diff carry mechanical detail.
- Show the exact message and staged file scope.
- Create the commit only after the user explicitly confirms that exact message and scope.
Safety
- Do not stage, amend, reset, rebase, or commit unrelated changes unless the user explicitly asks.
- If staged work contains unrelated topics, explain the split and ask which subset to commit rather than producing a misleading umbrella message.
- If no changes are staged, report that fact and do not substitute the working-tree diff.
Team use
This is a bounded single-artifact task. Complete it yourself; do not request an agent team.
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 · +2 lines ec121fd5f884
- 1mo ago Changed · -1 lines · -28 tokens per session 3744972b8e9d
- 1mo ago First seen · 28 lines · 61 tokens per session scan A cb29d1095e6f
commit is a skill published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 296 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-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.
dev-commit
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.