Borrowing it
Nothing to install: this file belongs to opensesh/karimo-overview. 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/opensesh/karimo-overview/main/.claude/commands/karimo/merge.mdgit clone --depth 1 https://github.com/opensesh/karimo-overviewWrote 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/opensesh/karimo-overview/merge)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/merge"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/merge.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.1 | $0.00000 | $0.07145 |
| Opus 5 | $0.00000 | $0.03572 |
| Sonnet 5 | $0.00000 | $0.01429 |
| Haiku 4.5 | $0.00000 | $0.00715 |
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 8d 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.
This is a copy
92% identical to merge — 100 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 875 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:merge — Feature Branch Merge Command
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
Arguments
--prd {slug}(required): The PRD slug to merge.--skip-validation(optional): Skip validation suite (use with caution).--auto-merge(optional): Automatically merge PR after creation (requires passing validation).
Prerequisites
Before merge, the PRD must be:
- Orchestrated via
/karimo:run(execution_mode: "feature-branch") - All tasks complete (status: "ready-for-merge")
- Feature branch exists with all task commits
Behavior
1. Validation
Verify the PRD is ready for merge:
# 1. Check status.json
status=$(jq -r '.status' .karimo/prds/{NNN}_{slug}/status.json)
execution_mode=$(jq -r '.execution_mode' .karimo/prds/{NNN}_{slug}/status.json)
feature_branch=$(jq -r '.feature_branch' .karimo/prds/{NNN}_{slug}/status.json)
if [ "$status" != "ready-for-merge" ]; then
echo "❌ PRD not ready for merge (status: $status)"
echo " Expected: ready-for-merge"
echo " Hint: Run /karimo:run --prd {slug} first"
exit 1
fi
if [ "$execution_mode" != "feature-branch" ]; then
echo "❌ PRD not using feature branch mode"
echo " This command is for v5.0 feature branch workflow only"
echo " For direct-to-main PRDs, tasks are already merged"
exit 1
fi
# 2. Check feature branch exists
if ! git ls-remote --heads origin "$feature_branch" | grep -q "$feature_branch"; then
echo "❌ Feature branch not found: $feature_branch"
exit 1
fi
# 3. Check all tasks merged to feature branch
open_prs=$(gh pr list --label karimo-${prd_slug} --base "$feature_branch" --state open --json number --jq 'length')
if [ "$open_prs" -gt 0 ]; then
echo "❌ $open_prs task PRs still open to feature branch"
gh pr list --label karimo-${prd_slug} --base "$feature_branch" --state open
echo " Wait for all task PRs to merge before running /karimo:merge"
exit 1
fi
echo "✓ PRD ready for merge"
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.
- 8d ago First seen · 875 lines · 0 tokens per session scan A 6a32efc8fdd7
merge is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 7,145 tokens. A static security scan graded it A with 0 findings. It is 92% identical to merge, differing in 100 lines, and is treated as a copy.
Other commands, from other repositories
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
update
Check for and apply KARIMO updates from GitHub releases.
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
commit
A Git commit command that reviews your changes and creates a Conventional Commits message, a standard format for describing what a change does.
worktree
A set of commands for managing Git worktrees, which are separate working folders linked to the same Git repository.
clean-branches
A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.