Herdr
Control Herdr, a terminal multiplexer for coding agents — inspect panes, tabs and workspaces
Curated by Skill Harbor — the operator's manual for Herdr, a terminal multiplexer built for coding agents: it organizes terminals into workspaces, tabs and panes, recognizes the agents running inside them, and exposes the current session through the `herdr` CLI — with strict rules (only act inside a Herdr-managed pane verified via `HERDR_ENV=1`, never control a session from outside, treat the installed binary as the authority for command syntax). By @herdrdev, listed here with credit to its creator. Honest caveats: the skill is useless without Herdr itself installed — it's documentation for the tool, not the tool; and it explicitly refuses to be used merely as a generic background-terminal trick. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
This skill is the operator's manual for Herdr, a terminal multiplexer built for coding agents, written by Herdr's own developer. It lets your agent inspect and control a Herdr session — workspaces, tabs and panes — through the herdr CLI, under strict rules about only acting inside Herdr-managed panes.
At a glance
| What it is | Documentation-as-a-skill for the Herdr tool: how its sessions are organized, how the CLI exposes the current session, and the safety rules for an agent operating it. It is not the tool itself. |
|---|---|
| Who it's for | Developers who run coding agents in Herdr and want an agent to work the session — checking panes, tabs and workspaces — instead of doing it by hand. |
| What you give it | Herdr itself installed and running — without it, the skill does nothing — and a task inside a session Herdr manages. |
| What you get | An agent that can inspect the session's workspaces, tabs and panes and act through the herdr CLI, verifying it is inside a Herdr-managed pane (HERDR_ENV=1) and treating the installed binary as the authority for command syntax. |
| Works with | Muse, installed from this page with the copy-paste install prompt, driving the Herdr multiplexer on your machine. |
| Cost | Free |
| Time | A few minutes to install. Session operations themselves are single CLI commands once Herdr is running. |
Example — taking stock of a busy agent session
An example of the kind of operation the manual documents, inside a session you already run:
- You ask your agent what is running across your Herdr session before you touch anything.
- The skill has it verify it is operating inside a Herdr-managed pane, then query the CLI for the session's workspaces, tabs and panes and which agents are running in them.
- It reports the layout back to you — and any further action stays inside that verified pane, never controlling the session from outside, per its rules.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 2563803Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Herdr installed on the machine (the skill documents the tool, it is not the tool itself) Install "Herdr" for me. Control Herdr, a terminal multiplexer for coding agents — inspect panes, tabs and workspaces Repository: https://raw.githubusercontent.com/herdrdev/herdr/2563803dca97c040beaf3dc3acdcb5a3221b4238/skills/herdr/SKILL.md Pinned version: install the code at commit 2563803dca97c040beaf3dc3acdcb5a3221b4238 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the herdrdev-herdr skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "herdrdev-herdr". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 2563803 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.