Borrowing it
Nothing to install: this file belongs to flupkede/codesearch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/flupkede/codesearch/master/.claude/commands/merge.mdgit clone --depth 1 https://github.com/flupkede/codesearchWrote 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/flupkede/codesearch/merge)<a href="https://agentmods.dev/commands/flupkede/codesearch/merge"><img src="https://agentmods.dev/badge/commands/flupkede/codesearch/merge/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/flupkede/codesearch/merge"><img src="https://agentmods.dev/badge/commands/flupkede/codesearch/merge.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.00023 | $0.01348 |
| Opus 5.5 | $0.00009 | $0.00539 |
| Sonnet 5.5 | $0.00005 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
merge 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/merge — land the current feature branch on develop
Run the project's merge workflow: verify docs are current, then bring the current
feature branch into develop through a pull request. This command does not tag a
release — tagging happens only in /release.
Branch & version facts (this repo)
- Flow:
feature/*|features/*|fix/*→ PR →develop→ (later) PR →master. masteris protected (.github/workflows/protect-master.yml): it accepts PRs only fromdeveloporrelease/*.- The pre-commit hook bumps the patch version (+1) and rebuilds the binary on feature
branches only (
feature/*,features/*,fix/*). Ondevelop/master/release/choreit runscargo fmtonly — no bump. So the feature-branch commit here fixes the release version; it carries forward unchanged through develop, master, and the tag.
Guardrails
- ABORT unless the current branch matches
feature/*,features/*, orfix/*— i.e. the branches the pre-commit hook version-bumps. Never run fromdevelop,master,release/*, orchore/*: on those the hook does not bump, so the version/CHANGELOG premise below would silently break. - NEVER push directly to
developormaster— everything lands via a PR. - NEVER pass
--no-verify/--no-gpg-sign— let the pre-commit hook run (it bumps + rebuilds). - Do NOT create or push a tag here. That is
/release's job. - Do NOT force-push.
Steps
-
Context
git rev-parse --abbrev-ref HEAD→ current branch. If it is NOTfeature/*,features/*, orfix/*, STOP with an error (see Guardrails).git fetch origin.- Compute the change set landing on develop:
git log origin/develop..HEAD --onelineplusgit status --shortfor uncommitted work. If there is nothing to land, report and STOP.
-
README up to date?
- Inspect the change set for user-facing changes: new/removed CLI flags or subcommands, behavior changes, new env vars, new supported languages, new MCP tools.
- Compare against
README.md. If anything is missing, wrong, or stale, UPDATEREADME.mdso it matches reality. Keep examples free of hardcoded config strings (per CLAUDE.md). - If README already matches, state that and move on.
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 · 92 lines · 23 tokens per session scan A 3f90a1d77477
merge is a command published in the GitHub repository flupkede/codesearch (96 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,348 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
improve
Run ONE iteration of the continuous-improvement loop — pick the highest-value backlog item, implement it, verify end-to-end, commit.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
event.batch_append
Append multiple events in one commit.
pre-commit-full
Command: /pre-commit-full Purpose: Comprehensive pre-commit validation orchestrating all error prevention checks.
aigon-research-spec-revise
You are the author-side agent. Review all pending spec-review: commits on the research spec, decide what to keep, and land one acknowledgement commit.
commit
Create a git commit with a well-crafted conventional commit message.