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.
/plugin marketplace add daman8271/the-perfect-orchestratornpx agentmods add plugins/daman8271/the-perfect-orchestrator/orchestratorgit clone --depth 1 https://github.com/daman8271/the-perfect-orchestratorWrote 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/plugins/daman8271/the-perfect-orchestrator/orchestrator)<a href="https://agentmods.dev/plugins/daman8271/the-perfect-orchestrator/orchestrator"><img src="https://agentmods.dev/badge/plugins/daman8271/the-perfect-orchestrator/orchestrator.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
orchestrator 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 6d 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.
What it actually says
{
"name": "orchestrator",
"description": "The /orch skill — turn your Claude Code session into the LEAD of a fleet: spawn N autonomous tmux workers, brief them, monitor them, and adversarially verify their results. Pairs with the orch CLI (install via the repo's install.sh).",
"version": "0.1.0",
"author": {
"name": "danny",
"url": "https://github.com/daman8271"
},
"homepage": "https://github.com/daman8271/the-perfect-orchestrator",
"repository": "https://github.com/daman8271/the-perfect-orchestrator",
"license": "MIT",
"keywords": ["orchestration", "multi-agent", "tmux", "fleet", "verification", "parallel"],
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 133 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago First seen · 15 lines scan A c3b1286ec0ce
orchestrator is a plugin published in the GitHub repository daman8271/the-perfect-orchestrator (1 stars, last pushed 2mo 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.
Other plugins, from other repositories
code-operations-plugin
Skills for code manipulation operations including line-based code transfer, bulk refactoring, and file analysis - converted from code-copy-mcp.
skill-creator-pro
Create, test, and iteratively improve Claude Code skills with the official lean coaching loop, an eval harness for benchmarking with variance analysis, and automated description-trigger optimization.
memory-kit
Persistent memory for Claude Code agents: a hot cache injected every session and held under three size caps, per-session handoffs, and agent-audited promotion into knowledge articles and rules. Carries the builder's layers too — executor/recon/idea-validator agents, session review, second opinion, agent QA and a…
brainstorm-panel
Assemble a task-specific panel of role-specialized agents and run a generate-critique-refine loop until the work converges on a strong result.
tune-repo-beta
Audit and tighten a repo's CLAUDE.md and guardrails so Claude Code works faster and more accurately in it: verify CLAUDE.md against reality, tighten the verify loop, add missing static guardrails, cut permission friction.
implement-issue
Drive a GitHub issue from branch to pull request with a language and build-tool agnostic workflow.