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-bulk-git-operationsgit 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-bulk-git-operations)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-bulk-git-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-bulk-git-operations/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-bulk-git-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-bulk-git-operations.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.00143 | $0.01488 |
| Opus 5.5 | $0.00057 | $0.00595 |
| Sonnet 5.5 | $0.00029 | $0.00298 |
| Haiku 4.5 | $0.00014 | $0.00149 |
Grade A, and why
repository-manager-bulk-git-operations 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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Manager — Bulk Git Operations
Fan-out git operations across every repository in a workspace, plus enterprise-scale remote enumeration, over the repository-manager MCP server. Long-running actions run as background jobs; poll them via the job status path.
When to use
- Clone / pull / push / add / commit across many repos in parallel.
- Run pre-commit hooks or a gated
commit_code(hooks then commit) across projects. - Phased push (push respecting inter-repo dependency phases).
enumerateevery repository across a GitLab instance / GitHub org into an ingest manifest — and natively ingest them into the KG as:GitRepositorynodes.
★ There is no arbitrary/raw git command action. rm_git_raw is accepted by
the action resolver (so it does not read as a typo) but the handler always returns
a refusal — "Raw host commands are permanently retired; use a typed repository-manager action through governed delegation." — regardless of
command. If the task genuinely has no typed action here, that is a signal to stop
and report the gap, not to route around it with a raw command.
When NOT to use
- Isolated per-session branch worktrees →
repository-manager-worktree-orchestration. - Install / build / validate / version-bump managed projects →
repository-manager-workspace-validation.
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 checkouts |
REPOSITORY_MANAGER_THREADS / RM_MAX_WORKERS |
optional | Parallelism for bulk ops |
RM_GATE_BEFORE_PUSH |
optional | Run the pre-push validation gate before pushing |
GITLAB_URL / GITLAB_PRIVATE_TOKEN |
for enumerate gitlab |
GitLab instance + PAT |
GITHUB_TOKEN / GH_TOKEN |
for enumerate github |
GitHub PAT |
GIT_OPERATIONSTOOL |
optional | Gate the git-operations tool tag 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.
- 7d ago Changed · -1 lines 510fb4bb70e8
- 1mo ago First seen · 112 lines · 143 tokens per session scan A 701734c6ac55
repository-manager-bulk-git-operations is a skill published in the GitHub repository Knuckles-Team/repository-manager (3 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 1,488 once invoked, about $0.0006 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
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
metagit-release-audit
Mandatory before calling work complete when the session changed repo files. Runs format, lint, tests, integration tests, context-aware pip-audit/bandit, and optional gitleaks via task qa:prepush. Use before push, release, or hand-off.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, atomic commits, worktrees, change summaries, and disciplined version control for AI agents and developer teams.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…