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.
git clone --depth 1 https://github.com/jjmartres/ai-coding-agentsWrote 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/commands/jjmartres/ai-coding-agents/commit-and-create-mr)<a href="https://agentmods.dev/commands/jjmartres/ai-coding-agents/commit-and-create-mr"><img src="https://agentmods.dev/badge/commands/jjmartres/ai-coding-agents/commit-and-create-mr/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/commands/jjmartres/ai-coding-agents/commit-and-create-mr"><img src="https://agentmods.dev/badge/commands/jjmartres/ai-coding-agents/commit-and-create-mr.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.00015 | $0.00244 |
| Opus 5.5 | $0.00006 | $0.00098 |
| Sonnet 5.5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
commit-and-create-mr 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 20d 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
Use glab skill and cli.
When command invoked, ALWAYS follow those steps:
- Use the
/commitcommand to commit your changes inside the current branch or worktree. - Create the merge request with
glab mr create. - Add detailed description of the merge request.
- Assign it to me.
- Open the merge request in my browser.
- Worktree Lifecycle:
- If operating inside a
.worktree/<branch>folder, the worktree remains active while the MR is open. - Once the MR is merged (or when user merges via
glab mr merge), execute the post-merge worktree cleanup:- Move the OpenCode session back to the primary repository root using
tools.opencode.session_move. - Remove the worktree:
git worktree remove .worktree/<branch> --force. - Prune worktrees:
git worktree prune. - Delete local branch:
git branch -d <branch> || git branch -D <branch>.
- Move the OpenCode session back to the primary repository root using
- If operating inside a
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.
- 20d ago Changed · +7 lines · +8 tokens per session 7908af7bfa42
- 1mo ago First seen · 14 lines · 7 tokens per session scan A 309629f39e95
commit-and-create-mr is a command published in the GitHub repository jjmartres/ai-coding-agents (49 stars, last pushed 9d ago), licensed MIT. It adds 15 tokens to every session and 244 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-30.
Other commands, from other repositories
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
resolve-review
Resolve reviewer feedback - from GitHub PRs, chat, or any reviewer.
make-pr
Commit staged changes, create or update a pull request.
pre-pr-check
Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist.
pr-description
Write a pull request description that helps reviewers: what changed, why, and how to verify, from a diff.
ship
Commit all changes and push to remote.