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 panayiotism/claude-harness --skill mergegit clone --depth 1 https://github.com/panayiotism/claude-harnessWrote 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/panayiotism/claude-harness/merge)<a href="https://agentmods.dev/skills/panayiotism/claude-harness/merge"><img src="https://agentmods.dev/badge/skills/panayiotism/claude-harness/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/skills/panayiotism/claude-harness/merge"><img src="https://agentmods.dev/badge/skills/panayiotism/claude-harness/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.00042 | $0.00843 |
| Opus 5 | $0.00021 | $0.00421 |
| Sonnet 5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00084 |
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 10d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge - Merge PRs, Close Issues, Clean Up Branches
Merge all open PRs and close related issues. Requires the gh CLI to be authenticated (gh auth status).
Phase 0: Get Repository Info
- Get GitHub owner/repo: use the cached values from the session context (injected at SessionStart). Only if absent, parse once from
git remote get-url origin(SSH:[email protected]:owner/repo.git, HTTPS:https://github.com/owner/repo.git). Use the owner/repo for ALL GitHub calls in this command.
Phase 1: Gather State
- Gather state:
- List all open PRs:
gh pr list --json number,title,headRefName,baseRefName,url,body - List all open issues with "feature" or "bugfix" labels:
gh issue list --label feature --label bugfix --json number,title - Read
.claude-harness/features/active.json:- Check
featuresarray for linked issue/PR numbers - Check
fixesarray for linked issue/PR numbers
- Check
- List all open PRs:
Phase 2: Build Dependency Graph
- Build dependency graph:
- For each PR, check if its base branch is another feature branch (not main/master)
- Order PRs so that dependent PRs are merged after their base PRs
- If PR A base is PR B head branch, merge B first
Phase 3: Pre-merge Validation
- Pre-merge validation for each PR (
gh pr view {number} --json state,mergeable,reviewDecision,statusCheckRollup):- CI status passes
- No merge conflicts
- Has required approvals (if any)
- Report any PRs that cannot be merged and why
Phase 4: Execute Merges
- Execute merges in dependency order:
- Merge the PR:
gh pr merge {number} --squash --delete-branch(--delete-branchremoves the remote branch and, when the repo is checked out on it, moves you back to the default branch) - Find and close any linked issues:
- Check PR body for "Closes #XX" or "Fixes #XX" (these auto-close on merge)
- Check
.claude-harness/features/active.jsonfor linked issues; close stragglers withgh issue close {number}
- For fix PRs:
- Close the fix issue
- Add comment to original feature issue:
gh issue comment {number} --body "Related fix merged: #{fix-issue} - {description}"
- Delete the local branch if it remains:
git branch -d {branch}(safe delete) - Update
.claude-harness/features/active.json:- For features: Set status="passing" in features array
- For fixes: Set status="passing" in fixes array
- Merge the PR:
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.
- 10d ago First seen · 74 lines · 42 tokens per session scan A fdb9f26f8286
merge is a skill published in the GitHub repository panayiotism/claude-harness (79 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 843 once invoked, about $0.0002 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-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.