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 maxence2997/mx-harness --skill mx-commitgit clone --depth 1 https://github.com/maxence2997/mx-harnessWrote 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/maxence2997/mx-harness/mx-commit)<a href="https://agentmods.dev/skills/maxence2997/mx-harness/mx-commit"><img src="https://agentmods.dev/badge/skills/maxence2997/mx-harness/mx-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/maxence2997/mx-harness/mx-commit"><img src="https://agentmods.dev/badge/skills/maxence2997/mx-harness/mx-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.00067 | $0.01113 |
| Opus 5.5 | $0.00027 | $0.00445 |
| Sonnet 5.5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
mx-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 24d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mx-commit
Trigger
/mx-commit # interactive — shows the drafts and waits for approval
/mx-commit --auto # non-interactive — commits all units immediately
Use --auto when invoked from an orchestrating skill (e.g. mx-flow). Use the default when invoked directly by the user.
Hard Rules (never violate)
- Never use
--no-verifyor--no-gpg-signunless the user explicitly requests it. - Never amend a commit that has already been pushed.
- Never commit files that likely contain secrets (
.env, credentials, private keys).
Step 1 — Load commit message rules
Read references/commit-message.md (located in the same directory as this SKILL.md).
This file contains the format, type definitions, rules, and examples to follow when drafting the commit message.
Step 2 — Inspect all pending changes
git status
git diff # unstaged
git diff --staged # staged
If there are no changes at all (nothing staged, nothing modified), tell the user and stop.
Step 3 — Group by logical concern
Analyse all pending changes (staged and unstaged together) and group them into one or more logical units. A logical unit is a set of files that together represent exactly one coherent change with a single type.
If all pending changes are one coherent change (single concern, one type), say so in one line and go straight to Step 4 with a single unit — no grouping analysis. Subject only, no body, when the change is trivial (typo, bump, comment); the 50-char subject limit and the type prefix still apply.
Rules:
- A logical unit maps to exactly one commit type (
feat,fix,refactor,doc,test,chore, …) - Files that belong to the same behaviour change belong in the same unit
- Test files and their corresponding implementation belong in the same unit
- Unrelated changes must be split into separate units
If changes span multiple logical units, plan the commit order (dependencies first).
Step 4 — Draft commit messages
What ships with it
2 files 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.
- 24d ago Changed 747e797153aa
- 1mo ago Changed · +14 lines · -11 tokens per session 14b9beb48d11
- 1mo ago First seen · 127 lines · 78 tokens per session scan A 21e0ae492ad1
mx-commit is a skill published in the GitHub repository maxence2997/mx-harness (5 stars, last pushed 24d ago), licensed MIT. It adds 67 tokens to every session and 1,113 once invoked, about $0.0003 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
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
flag-cleanup
Weekly reusable-session feature-flag cleanup for {{targetrepo}}. Inventories every feature flag, classifies each as fully rolled out, long dead, partial rollout, or active experiment, removes the flag and the dead branch it guards on an isolated branch when the suite is green, and opens a PR — never touching a flag…
git-workflow
Git best practices, branching strategies, commit conventions, and code review patterns.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
implement-suggestion
Implements review-comment suggestions across one or more PRs. Multi-PR mode (default when $ARGUMENTS holds PR URLs; empty $ARGUMENTS auto-detects the active PR) resolves a worktree per PR, fetches every actionable comment from human teammates AND AI review bots (claude[bot], coderabbitai[bot], …), validates each…