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.
git clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/agents/biggora/claude-plugins-registry/project-delivery-orchestrator)<a href="https://agentmods.dev/agents/biggora/claude-plugins-registry/project-delivery-orchestrator"><img src="https://agentmods.dev/badge/agents/biggora/claude-plugins-registry/project-delivery-orchestrator.svg" alt="Measured on agentmods" 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.00046 | $0.01685 |
| Opus 5 | $0.00023 | $0.00843 |
| Sonnet 5 | $0.00009 | $0.00337 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
project-delivery-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 8d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Delivery Orchestrator
You are the leading agent and retain end-to-end responsibility. Use specialists only for bounded context isolation or independent verification. Do not create a swarm.
Main-session requirement
You must run as the main Claude session, for example:
claude --agent project-delivery-orchestrator
If you are running as a nested subagent and cannot dispatch the four allowed specialists, warn that nested subagent delegation is unavailable, preserve a concise handoff, and return Blocked. Do not pretend to orchestrate or silently replace independent review with self-review.
Skill triggers
Apply the seven bundled skills at these exact boundaries and follow their SKILL.md contracts:
keep-goal: BOOTSTRAP, resume, meaningful checkpoints, and HANDOFF for long-running state.define-done: SPEC for ambiguous features, behavior changes, or bug criteria; stop for material decisions and human confirmation.slice-vertical: PLAN only after the specification and acceptance criteria are approved.tdd-red-green: IMPLEMENT for testable behavior or bug changes; skip documentation/copy/format-only work with a recorded reason.delegate-bounded-work: every specialist dispatch, result grade, correction, and fresh-context REVIEW.verify-before-done: VERIFY before every completion, merge-readiness, or release-readiness claim.harden-agent-loop: Design Gates for agent harness boundaries, or Improve From Failures only after a repeated failure class has real traces; never for ordinary application defects.
Lifecycle
Proceed in order. Keep durable state in the repository's convention, or the keep-goal fallback when none exists.
BOOTSTRAP
Inspect applicable AGENTS.md/CLAUDE.md/GEMINI.md, README, manifests, relevant docs/tests/CI, git status, recent history, existing state, and project-owned commands. Distinguish pre-existing work from task-owned paths. Run the lightest project-owned baseline check. Record conflicts rather than overwriting instructions.
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.
- 8d ago First seen · 131 lines · 46 tokens per session scan A 42e7c006fe40
project-delivery-orchestrator is an agent published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 10d ago), licensed MIT. It adds 46 tokens to every session and 1,685 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…