Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-worktree-orchestration)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-worktree-orchestration"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-worktree-orchestration/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-worktree-orchestration"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-worktree-orchestration.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.00128 | $0.01722 |
| Opus 5 | $0.00064 | $0.00861 |
| Sonnet 5 | $0.00026 | $0.00344 |
| Haiku 4.5 | $0.00013 | $0.00172 |
Grade A, and why
repository-manager-worktree-orchestration 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 12d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Manager — Worktree Orchestration
Manage git worktrees for concurrent multi-session development over the
repository-manager MCP server. Each session works a repo in its own worktree on its
own branch under /home/apps/worktrees/<repo>/<branch> (shared .git, no re-clone),
leaving the canonical checkout on its default branch so a working-tree reset never
disturbs in-flight work.
When to use
- Open an isolated worktree/branch for a new session (
add, orbulk_addacross repos). - List existing worktrees for one repo or the whole workspace (
list). - Classify worktrees as merged / active / stale / dangling before pruning (
audit). - Bring a worktree up to date with its base (
sync), or merge finished work back (merge). - Remove a worktree and optionally its branch (
remove), or prune stale admin pointers (prune).
When NOT to use
- Running a unit of work as an isolated lane (isolation exports, the traps, preflight,
finishing) →
repository-manager-lane-lifecycle. That is the skill to reach for first; this one is the raw verb surface underneath it. - Landing a branch, gates, or conflict resolution →
repository-manager-merge-and-reconcile. - Waves across many repos, mass audits and prunes, concurrency sizing →
repository-manager-fleet-scale-operations. - Bulk clone / pull / push / commit across repositories →
repository-manager-bulk-git-operations. - Install / build / validate / version-bump managed projects →
repository-manager-workspace-validation. - Editing files inside a worktree — that is ordinary file work, not this tool.
Prerequisites & environment
Connect via the mcp-client skill against the repository-manager MCP server.
| Variable | Required | Notes |
|---|---|---|
REPOSITORY_MANAGER_WORKSPACE / WORKSPACE_PATH |
✅ | Workspace root holding the canonical checkouts |
REPOSITORY_MANAGER_WORKTREE_ROOT |
✅ | Root under which linked worktrees live (/home/apps/worktrees) |
REPOSITORY_MANAGER_DEFAULT_BRANCH |
optional | Base branch (default main) |
WORKSPACE_MANAGEMENTTOOL / PROJECT_MANAGEMENTTOOL |
optional | Gate the tool tags on |
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.
- 12d ago First seen · 122 lines · 128 tokens per session scan A b836342a3745
repository-manager-worktree-orchestration is a skill published in the GitHub repository Knuckles-Team/repository-manager (2 stars, last pushed 14d ago), licensed MIT. It adds 128 tokens to every session and 1,722 once invoked, about $0.0006 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
status
Show a comprehensive project status dashboard: task queue, blocked items, session state, verification, and git status.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
metagit-rewrite-campaign
Orchestrate a reference-implementation rewrite across source and target repos using campaigns, parity registry conventions, objectives, and subagent handoffs.
metagit-control-center
Use when running metagit as an MCP control center for multi-repo awareness, guarded sync, and operational knowledge across ongoing agent tasks.
metagit-sharing-state
Configure shared coordination state (objectives, handoffs, approvals, events) across multiple agents and machines via METAGITSTATEURL, optional DynamoDB / MongoDB DocumentStore backends, and the ops HTTP path. Use when Hermes subagents, CI runners, or humans must see the same objective queue without Syncthing JSON…