shift-leader

An orchestrator for coordinating several coding agents and pull requests, which are proposed code changes reviewed before merging.

In plain words
What is it for?
Use it to run a multi-agent development effort, dispatch independent tasks, track progress across pull requests, and coordinate follow-up work.
Why use it?
It keeps parallel work organized by assigning separate work areas, moving through phases only after pull requests are merged, and asking the user about genuine blockers.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add ShivaeDev/pardes
agentmods
npx agentmods add plugins/shivaedev/pardes/shift-leader
Clone the repo
git clone --depth 1 https://github.com/ShivaeDev/pardes

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

shift-leader 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 yesterday.

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.

plugins/shift-leader/.claude-plugin/plugin.json · 11 lines

What it actually says

{
  "author": {
    "name": "ShivaeDev"
  },
  "description": "Run as the autonomous shift leader of a multi-PR / multi-agent effort — maximize progress, reach the away user only via AskUserQuestion, gate phases on PR merges (never merge yourself), and dispatch file-disjoint parallel worktree agents at high velocity.",
  "keywords": ["orchestration", "multi-agent", "parallel-worktrees", "pr-gating", "autonomy"],
  "license": "MIT",
  "name": "shift-leader",
  "version": "0.2.0"
}
Changes

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.

  1. yesterday First seen · 11 lines scan A 664c472ebeda

Subscribe to this mod's changes

shift-leader is a plugin published in the GitHub repository ShivaeDev/pardes (5 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.