Skip to content
Back to search

herdr-agent-pool

MarketplaceWorks with Claude CodeGitHub

Claude Code plugin for many agents on one repo inside herdr: a coordinator, a pool of parallel integrators with atomic PR claims and a merge lock, negotiated machine resources, and cleanup of merged worktrees

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 19 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/R0drig0V1/herdr-agent-pool with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/R0drig0V1/herdr-agent-pool'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/r0drig0v1--herdr-agent-pool/badge.svg)](/listings/r0drig0v1--herdr-agent-pool)

HTML

<a href="/listings/r0drig0v1--herdr-agent-pool"><img src="/api/listings/r0drig0v1--herdr-agent-pool/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Requirements: herdr (built against 0.9.5) with Claude Code running inside it (`HERDR_ENV=1`), `git`, `bash`, `jq`, `python3` (3.9+) and the GitHub CLI `gh`.

Once per machine, herdr, if missing: `curl -fsSL https://herdr.dev/install.sh | sh` (other methods: https://herdr.dev/tui/docs/install/).

Then, in each repository you want to set up, one command from inside it:

curl -fsSL https://raw.githubusercontent.com/R0drig0V1/herdr-agent-pool/main/install.sh | bash
# or, from a local clone:  bash /path/to/herdr-agent-pool/install.sh

It does the whole setup and ends with a report of this machine and the steps that are left:

- Copies the project-owned files without overwriting: an existing file is kept and listed (`--force` overwrites, without a backup). It never writes through a symbolic link or outside the repository. - Enables the plugin in `.claude/settings.json` and sets the plugins it must not run next to, `multi-agent@claude-code-multi-agent` and `multi-agent-herdr@claude-code-herdr`, to `false` there. - Installs the plugin for the project with the `claude` CLI when it is not installed yet (`--no-plugin` skips that). Without the CLI it prints the two commands: `claude plugin marketplace add R0drig0V1/herdr-agent-pool` and `claude plugin install herdr-agent-pool@herdr-agent-pool --scope project`. - Checks `jq`, `python3`, `gh`, herdr and herdr's Claude integration. It never installs herdr; when the integration is missing it asks before running `herdr integration install claude`. - `--dry-run` previews everything, asks nothing and changes nothing.

What is left is yours: fill in the TODOs of `CLAUDE.md`, put your checks in `scripts/check.sh`, commit, and launch the integrator inside herdr with `scripts/integrator.sh` (pool mode: `scripts/coordinator.sh`). `/herdr-agent-pool:setup` runs the same checks from inside Claude Code later (after a plugin update, or to diagnose a project) and reviews the project's CI; it is not a required step.

To try the plugin without installing: `claude --plugin-dir /path/to/herdr-agent-pool/plugin`.

**"Plugin not found in marketplace".** The plugin id ends in the marketplace name, so the marketplace must be registered as `herdr-agent-pool`. A machine that already knows this GitHub repository under another name (it was set up before the rename, or the user's `~/.claude/settings.json` declares it so in `extraKnownMarketplaces`) answers `claude plugin marketplace add R0drig0V1/herdr-agent-pool` with "already on disk" and adds nothing, and the install then fails with "not found in marketplace". The installer detects this, names the other marketplace and asks before removing it; removing a marketplace also uninstalls, on that machine, the plugins installed from it. By hand (`claude plugin marketplace list` shows the name):

claude plugin marketplace remove <the other name>
claude plugin marketplace add R0drig0V1/herdr-agent-pool
claude plugin install herdr-agent-pool@herdr-agent-pool --scope project

**Scope.** A project-scope install lives in that repository's `.claude/settings.json`. With a user-scope install the skills are listed everywhere, but the guard and SessionStart hooks only act in repositories whose `.claude/settings(.local).json` maps `herdr-agent-pool@herdr-agent-pool` to `true` in `enabledPlugins` (`settings.local.json` wins, so `false` there turns them off), and `dispatch`, `pr` and `integrate` stop outside herdr. `notify.sh` (sound + bell) runs in every session where the plugin is installed. herdr's own Claude integration (`~/.claude/hooks/`) and config (`~/.config/herdr/`) are global and are not touched by this plugin.

Configuration

By default pull requests target `main`, the integrator's herdr agent is `integrator-<repo>` and worktrees are `../<repo>-<name>`. A project that works otherwise says so in the optional, versioned `.claude/herdr-agent-pool.json` at the root of its main

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.