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/sgaunet/claude-plugins/auto-mrnpx skills add sgaunet/claude-plugins --skill auto-mrgit clone --depth 1 https://github.com/sgaunet/claude-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/sgaunet/claude-plugins/auto-mr)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/auto-mr"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/auto-mr.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 | $0.00039 | $0.00926 |
| Opus 5 | $0.00019 | $0.00463 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
auto-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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
auto-mr Skill
Push the current branch, create a MR/PR on GitHub, GitLab, or Forgejo, wait for the CI pipeline, merge, and clean up the branch — all via the auto-mr CLI.
For git.sylvlab.fr repositories, the underlying auto-mr binary routes via the fgj CLI; GitHub and GitLab remotes are handled automatically as before. Platform detection and routing are handled entirely by the binary — this skill does not branch on the host.
CLI Reference
Flags:
--labels string Comma-separated label names (e.g., "bug,enhancement")
--list-labels List all available labels and exit
-l, --log-level string Set log level (debug, info, warn, error) [default "info"]
--msg string Custom message for MR/PR (overrides commit message selection)
--no-squash Disable squash merge (default: squash enabled)
--pipeline-timeout string Pipeline/workflow timeout [default "30m"]
-v, --version Print version and exit
Workflow
Step 1: Pre-flight Checks
Verify auto-mr is installed:
auto-mr --version
If the command fails, abort with:
auto-mris not installed. Install it from https://github.com/sgaunet/auto-mr and ensure it is in your PATH.
Get current branch:
git rev-parse --abbrev-ref HEAD
If the branch is main, master, or develop, warn the user:
Warning: you are on a protected branch (
<branch>).auto-mris intended for feature branches.
Check for uncommitted changes:
git status --porcelain
If the working tree is dirty, warn the user:
Warning: you have uncommitted changes. Consider committing or stashing them before creating a MR/PR.
Step 2: Label Discovery (early exit)
If --list-labels is present in the arguments:
auto-mr --list-labels
Display the output and return. Do not proceed further.
Step 3: Assemble Command
Base command: auto-mr
Append all provided flags verbatim (e.g., --no-squash, --msg "fix: ...", --labels "bug,help wanted").
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.
- 5d ago First seen · 103 lines · 39 tokens per session scan A 2dc7d8a4a016
auto-mr is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 926 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.