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 skills add joris887/exosuit --skill merge-upgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/skills/joris887/exosuit/merge-up)<a href="https://agentmods.dev/skills/joris887/exosuit/merge-up"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/merge-up/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/skills/joris887/exosuit/merge-up"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/merge-up.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.00095 | $0.01199 |
| Opus 5 | $0.00048 | $0.00600 |
| Sonnet 5 | $0.00019 | $0.00240 |
| Haiku 4.5 | $0.00010 | $0.00120 |
Grade A, and why
merge-up 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
merge-up
Merge the current stream's branch into the parent it was created from, then
fast-forward the current branch back up to the parent. Safe across worktrees:
the parent is usually checked out in another worktree, so the merge runs there
via git -C rather than checking the parent out here (git forbids that).
Step 1 — Identify branches
B="$(git rev-parse --abbrev-ref HEAD)"
echo "current branch: $B"
- If
BisHEAD(detached), STOP — tell the user to check out a branch. - Resolve the parent
P:P="$(git config "branch.$B.exosuitParent" || true)"- If empty, fall back to stripping the last
-<suffix>(e.g.sprint-3-a→sprint-3) and verify it exists withgit show-ref --verify --quiet refs/heads/<cand>. - If still unresolved or ambiguous, ASK the user which branch is the parent.
- If empty, fall back to stripping the last
- If
P == BorPdoesn't exist, STOP and report.
Step 2 — Pre-flight cleanliness (both worktrees)
git status --porcelain # current worktree — must be empty
- If the current worktree is dirty, STOP: the skill merges committed work only. Tell the user to commit or stash first.
- Locate the parent's worktree dir:
Find the entry whose branch isgit worktree list --porcelainrefs/heads/$P; call its pathPDIR.- If
Pis not checked out in any worktree, STOP and tell the user to check it out in a worktree first (the merge needs a working tree to run in).
- If
- Verify the parent worktree is clean:
git -C "$PDIR" status --porcelainmust be empty. If dirty, STOP and report which worktree/path needs attention.
Step 3 — Merge current branch into parent (true merge)
Run the merge in the parent's worktree:
git -C "$PDIR" merge "$B"
- This keeps
B's individual commits (fast-forwards when possible). - On "Already up to date." → nothing to merge; tell the user and SKIP to Step 5.
- On conflict: run
git -C "$PDIR" merge --abort, then STOP and report the conflicting files. Offer to help resolve, but do NOT leave the parent worktree in a half-merged state without telling the user. - On success, show
git -C "$PDIR" log --oneline -3.
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 · 108 lines · 95 tokens per session scan A 354665bb6d96
merge-up is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 20d ago), licensed MIT. It adds 95 tokens to every session and 1,199 once invoked, about $0.0005 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 skills, from other repositories
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.