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 commands/gantisstorm/essentials-claude-code/mr-description-creatorgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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.00017 | $0.00757 |
| Opus 5 | $0.00009 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
mr-description-creator 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 2d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MR/PR Description Creator
Generate MR/PR descriptions and apply directly using gh (GitHub) or glab (GitLab) CLI.
Requires: gh or glab CLI installed and authenticated.
Related Skills
/github-cli <action>— GitHub CLI wrapper/gitlab-cli <action>— GitLab CLI wrapper
Arguments
--template "markdown"- Custom template for description- (none) - Uses default template
Instructions
Step 1: Detect Platform
git remote get-url origin 2>/dev/null
github.comorghe.→ GitHub → useghgitlab→ GitLab → useglab- Unclear → Ask user
Step 2: Validate Environment
GitHub:
gh auth status
GitLab:
glab auth status
- If not installed: Report install link
- If not authenticated: Report auth command
- If on main/master: Report error (need feature branch)
Step 3: Determine Action
# GitHub
gh pr view --json number -q '.number' 2>/dev/null
# GitLab
glab mr view --output json 2>/dev/null | jq -r '.iid'
- MR/PR exists →
update - No MR/PR →
create
Step 4: Gather Git Context
git log main..HEAD --oneline
git diff main...HEAD --stat
git rev-list --count main..HEAD
Step 5: Launch Agent
Launch background agent with gathered context:
Generate MR/PR description:
Platform: <github or gitlab>
CLI: <gh or glab>
Action: <create or update>
Branch: <current> -> <base>
Template: <custom or "default">
Commits: <count>
REQUIRED Task tool parameters:
subagent_type: "essentials:mr-description-creator-default"
run_in_background: true
prompt: "Generate MR/PR description:\nPlatform: <platform>\nCLI: <cli>\nAction: <action>\nBranch: <branch info>\nTemplate: <template>\nCommits: <count>"
Output a status message like "Generating description..." and end your turn. The system wakes you when the agent finishes.
Step 6: Report Result
## MR/PR <CREATED/UPDATED>
**Platform**: <GitHub or GitLab>
**URL**: <url>
**Branch**: <current> -> <base>
View: <gh pr view --web OR glab mr view --web>
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.
- 2d ago First seen · 126 lines · 17 tokens per session scan A 264f2a2f39c1
mr-description-creator is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 17 tokens to every session and 757 once invoked, about $0.0001 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 commands, from other repositories
analyze-repo
Analyze an existing repository's structure, conventions, and guardrails.
go-test
Go TDD workflow with table-driven tests.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
doctor
Run IJFW health check (files, MCP server, hooks, memory, caps, framing).