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/foudrayelias-ALPHA/pleachWrote 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/foudrayelias-alpha/pleach/pleach-merge)<a href="https://agentmods.dev/commands/foudrayelias-alpha/pleach/pleach-merge"><img src="https://agentmods.dev/badge/commands/foudrayelias-alpha/pleach/pleach-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/foudrayelias-alpha/pleach/pleach-merge"><img src="https://agentmods.dev/badge/commands/foudrayelias-alpha/pleach/pleach-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.00010 | $0.00213 |
| Opus 5 | $0.00005 | $0.00106 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
pleach-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 9d 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.
What it actually says
Merge two session branches: $ARGUMENTS
- Run
!pleach merge $ARGUMENTS --dry-runfirst and show the user the plan — the merge base, how it was derived, and its confidence. - Point out explicitly if the base is marked
drifted(the parent kept working after the branch point, so the base includes context the branches never shared) orunverified(transcript synthesis has not been confirmed on this machine —pleach doctor --test-synthesissettles it). - Ask the user to confirm before dispatching.
- On confirmation, run
!pleach merge $ARGUMENTSand tell them to watch it withclaude agents.
The merge agent runs read-only by default. Do not pass --allow-writes unless
the user explicitly asks for it.
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.
- 9d ago First seen · 20 lines · 10 tokens per session scan A 4ead2656c86f
pleach-merge is a command published in the GitHub repository foudrayelias-ALPHA/pleach (0 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 213 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-31.
Other commands, from other repositories
watch-ci
Spawn a background Haiku-backed subagent to watch CI for the current branch (or specified target). Provider-agnostic — the subagent inspects project signals to identify the CI system (GitHub Actions, GitLab CI, CircleCI, etc.) and picks the right CLI. Returns immediately; reports back when CI reaches a terminal state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
done
Finish a task - document, create PR or merge, close.
worktree
Worktree lifecycle management - create, list, remove, info on interactive worktrees.
create-release-note.en
Generate release notes from PRs and commits.