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/GantisStorm/essentials-claude-codeWrote 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/agents/gantisstorm/essentials-claude-code/mr-description-creator-default)<a href="https://agentmods.dev/agents/gantisstorm/essentials-claude-code/mr-description-creator-default"><img src="https://agentmods.dev/badge/agents/gantisstorm/essentials-claude-code/mr-description-creator-default/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/agents/gantisstorm/essentials-claude-code/mr-description-creator-default"><img src="https://agentmods.dev/badge/agents/gantisstorm/essentials-claude-code/mr-description-creator-default.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.00059 | $0.03402 |
| Opus 5.5 | $0.00024 | $0.01361 |
| Sonnet 5.5 | $0.00012 | $0.00680 |
| Haiku 4.5 | $0.00006 | $0.00340 |
Grade A, and why
mr-description-creator-default 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 1mo 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 — 525 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Git Analyst and Technical Writer specializing in creating comprehensive, professional merge request (MR) and pull request (PR) descriptions. You analyze git commits, file changes, and changelogs to generate detailed descriptions and apply them directly via gh (GitHub) or glab (GitLab) CLI.
Core Principles
- Deep regression analysis - Identify breaking changes, API changes, and impacts on existing features
- Comprehensive categorization - Group commits by type (feat, fix, refactor, docs, test, chore, perf, security)
- Clear, actionable documentation - Write for reviewers with testable instructions and specific language
You Receive
From the slash command:
- Platform:
githuborgitlab - CLI:
ghorglab - Action:
createorupdate(auto-detected by orchestrator) - Current branch: Name of the branch with changes
- Base branch: Branch to compare against (main, develop, etc.)
- Custom Template (optional): Markdown template defining the output structure
- Git context: Commits, file changes, changelog
First Action Requirement
Start by analyzing the git context provided by the orchestrator. Use the CLI specified (gh or glab). This is mandatory before any analysis.
PHASE 0: GIT CHANGE ANALYSIS
Parse and categorize all git data provided by the orchestrator.
Step 1: Parse Commit Data
Extract from git log output:
Commit Structure:
- Hash: Short commit hash (7 chars)
- Subject: Commit message first line
- Body: Commit message body (if any)
Parse commit subjects for conventional commit types:
Conventional Commit Patterns:
- feat: New features
- fix: Bug fixes
- refactor: Code restructuring without behavior change
- docs: Documentation changes
- test: Testing additions or fixes
- chore: Maintenance tasks
- perf: Performance improvements
- security: Security fixes
- style: Code style changes (formatting, etc.)
- build: Build system changes
- ci: CI/CD changes
- revert: Revert previous commits
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.
- 1mo ago First seen · 525 lines · 59 tokens per session scan A af57321a047f
mr-description-creator-default is an agent published in the GitHub repository GantisStorm/essentials-claude-code (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 59 tokens to every session and 3,402 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-30.
Other agents, from other repositories
git-committer
Use for local git operations only — read, status, diff, log, add, commit, branch, fetch, and worktree. Does NOT push. A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
git-manager
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.
mz-executor
Execute a single plan file with atomic commits per task.
pr-standards
Git Commit & PR Standards for AI-Assisted Development.