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/opensesh/karimo/mergegit clone --depth 1 https://github.com/opensesh/KARIMOWrote 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/merge)<a href="https://agentmods.dev/commands/opensesh/karimo/merge"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/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 | $0.00000 | $0.07865 |
| Opus 5 | $0.00000 | $0.03932 |
| Sonnet 5 | $0.00000 | $0.01573 |
| Haiku 4.5 | $0.00000 | $0.00787 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- merge — 92% identical, 100 lines differ
How it starts
The opening of the file, as written. The whole thing — 963 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.
- 5d ago First seen · 963 lines · 0 tokens per session scan A 669b25645015
merge is a command published in the GitHub repository opensesh/KARIMO (284 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 7,865 tokens. 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
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
test-mcp
Test MCP server connection and all tools.
audit-components
Scan all feature components against the 7 architecture principles in .claude/reference/react-architecture.md, produce a structured report with pass/fail per check, and output a prioritized fix plan.
feature-dev
Guided feature development with design-first thinking and systematic architecture.
audit-devprops
Scan the codebase for devProps compliance and produce a structured report grouped by section, with a percentage summary and an explicit exemption list.
code-review
Code review a pull request with BOS design system awareness.