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 Knuckles-Team/repository-manager --skill repository-manager-merge-and-reconcilegit clone --depth 1 https://github.com/Knuckles-Team/repository-managerWrote 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/knuckles-team/repository-manager/repository-manager-merge-and-reconcile)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-merge-and-reconcile"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-merge-and-reconcile/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/knuckles-team/repository-manager/repository-manager-merge-and-reconcile"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-merge-and-reconcile.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.00163 | $0.03281 |
| Opus 5.5 | $0.00065 | $0.01312 |
| Sonnet 5.5 | $0.00033 | $0.00656 |
| Haiku 4.5 | $0.00016 | $0.00328 |
Grade A, and why
repository-manager-merge-and-reconcile 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 11d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Manager — Merge & Reconcile
Landing is the one operation a lane cannot do independently, so it goes through one serialized queue per repository. This skill is how to use it, and — the harder half — how to reconcile when what you wrote and what landed while you were writing it disagree.
When to use
- A branch is ready to land.
- A merge conflicts, or the queue rejected your candidate.
- A gate is red and you must decide whether that failure is yours.
- You need to know what a branch will actually do once merged.
When NOT to use
- Opening/isolating/diagnosing a lane →
repository-manager-lane-lifecycle. - Sweeping worktrees across the workspace →
repository-manager-fleet-scale-operations.
The one path in
repository-manager --merge-queue enqueue --repo-path . # offer the branch
repository-manager --merge-queue status --repo-path . # watch it
repository-manager --merge-queue config --repo-path . # validate the gates
repository-manager --merge-queue withdraw --repo-path . --queue-branch <b>
MCP: rm_merge_queue_<action>(repo_path=…). Standalone driver, suitable as a
systemd/CronJob ExecStart: python -m repository_manager.merge_queue run --path <repo>.
Enqueued is not a to-do item. A scheduler drains every ~5 minutes: it gates the candidate as merged, fast-forwards the base, and prunes the worktree and the branch. Do not hand-merge because the queue feels slow — two lanes hand-merging is how a resolution gets orphaned.
Exit 75 (EX_TEMPFAIL) means another runner holds this repository's
reconciliation-merge lease. Defer. Do not retry in a loop.
Mechanism vs gates — and why this matters to you
MECHANISM (repository_manager/merge_queue.py — generic, one implementation)
enqueue / status / withdraw / run / config differential gating vs a base ref
per-repo candidate store regenerate-on-land
the reconciliation-merge lease guarded prune
optimistic batching + bisection fast-forward-only landing
GATES (<repo>/.mergequeue.yaml — declarative, per project)
a command, a tier, a timeout, and HOW to compare its result to the base
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago Changed 3d3c9ba50aca
- 2mo ago First seen · 243 lines · 163 tokens per session scan A 1a9764e3e54a
repository-manager-merge-and-reconcile is a skill published in the GitHub repository Knuckles-Team/repository-manager (3 stars, last pushed yesterday), licensed MIT. It adds 163 tokens to every session and 3,281 once invoked, about $0.0007 per session on Opus 5.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
gitlab-merge-request-review
Review and merge GitLab merge requests via the gitlab-api MCP server — by default the MRs assigned to you or where you are a reviewer, optionally scoped to a project, group, or the whole instance. Read an MR, gate it on a green pipeline (pipeline → jobs → job log), then approve, accept/merge, or set…
release
MUST READ before preparing a release commit or GitHub release -- the blocking GitHub preflight (dev/releasepreflight.py), project.save() versioning, changelog, README, template sync verification, fresh-install smoke, and the post-push GitHub release procedure (references/github-release.md).
merge-divergent-tox
Merge or compare two divergent TouchDesigner .tox/.toe binaries that git cannot three-way-merge. Load when a merge/rebase conflicts on a .tox or .toe, when asked to merge, port, reconcile, or diff two versions of a TD component, or when comparing a component across branches, machines, or TD builds.
servicenow-studio-gitlab-app
Wire a ServiceNow scoped app (App Engine Studio / Fluent) to a GitLab repository and drive its promotion two ways — Path A: native Studio source control (servicenowsourcecontrol → importrepository / applyremotesourcecontrolchanges, handing off to servicenowcicd for publish/install), or Path B: GitLab-CI-driven…
gitlab-api-development
Develop, test, gate, and release the GitLab REST and GraphQL connector. Use this skill when changing API mappings, governed MCP tools, authentication, tenant selection, KG ingestion, packaged content, or repository gates.
gitlab-merge-request-create
Open a new GitLab merge request against a project via the gitlab-api MCP server — from a source branch into a target branch, with title, description, assignees, reviewers, labels, and remove-source-branch/squash options. Use when the agent must create/open an MR for a project. Do NOT use to review, approve, or merge…