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-prgit 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-pr)<a href="https://agentmods.dev/skills/maxence2997/mx-harness/mx-pr"><img src="https://agentmods.dev/badge/skills/maxence2997/mx-harness/mx-pr/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-pr"><img src="https://agentmods.dev/badge/skills/maxence2997/mx-harness/mx-pr.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.00057 | $0.02721 |
| Opus 5.5 | $0.00023 | $0.01088 |
| Sonnet 5.5 | $0.00011 | $0.00544 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
mx-pr 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mx-pr
Trigger
/mx-pr <name> ← draft PR for named feature
/mx-pr ← infer from active spec or ask
Orchestrated mode
This skill has interactive pauses (Steps 3, 4 and 5). When invoked from
an orchestrator that declares auto-proceed for its PR gate (e.g. mx-flow
GATE 4), the orchestrator's gate table overrides those pauses: still
display everything you would have shown, but proceed without waiting —
pause only if you cannot determine how to proceed (no remote, ambiguous
platform, missing credentials). "Cannot determine" means the command would
fail or target the wrong repo — not that you would like a second opinion.
If git remote -v names exactly one host, that is the platform; do not
ask. When invoked directly by the user, the pauses apply as written.
Step 5 publishes. That is the irreversible step: under auto-proceed, publish without asking, but say what you are about to push and to which base before you run it.
Because auto-proceed removes the human review of the draft, add one check in its place: if a subagent tool (Agent/Task) is available, spawn a fresh read-back agent on the draft before Step 5 — criteria: every factual claim traces to spec.md or the git log; every referenced issue number exists; the body names no local-only files (Step 2's committed-files-only rule). Fix findings before pushing. If no subagent tool exists, re-check the draft yourself against those criteria and label the result "self-checked, single-context" in the output.
Path resolution
Resolve two base directories before any file operation:
REPO_ROOT=$(git rev-parse --show-toplevel)
PROJECT=$(basename "$REPO_ROOT")
| Variable | Path | Used for |
|---|---|---|
GLOBAL_MX |
~/.mx/<project>/<name>/ |
Reading spec.md (permanent) |
LOCAL_MX |
<repo-root>/.mx/<name>/ |
Writing PR drafts to tmp/ (ephemeral) |
Step 1 — Gather context
Read GLOBAL_MX/spec.md (~/.mx/<project>/<name>/spec.md) for the
What/Why/How summary.
What ships with it
3 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.
- 23d ago Changed · -13 lines · -10 tokens per session f0d245a77e15
- 1mo ago Changed · +37 lines · +1 tokens per session 2b023c4d2061
- 1mo ago First seen · 294 lines · 66 tokens per session scan A 8cadf14af936
mx-pr is a skill published in the GitHub repository maxence2997/mx-harness (5 stars, last pushed 24d ago), licensed MIT. It adds 57 tokens to every session and 2,721 once invoked, about $0.0002 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…
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.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".