Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dansasser/claude-code-marketplacenpx agentmods add agents/dansasser/claude-code-marketplace/pr-prep-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/agents/dansasser/claude-code-marketplace/pr-prep-orchestrator)<a href="https://agentmods.dev/agents/dansasser/claude-code-marketplace/pr-prep-orchestrator"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/pr-prep-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.00043 | $0.01516 |
| Opus 5 | $0.00022 | $0.00758 |
| Sonnet 5 | $0.00009 | $0.00303 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
pr-prep-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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Prep Orchestrator
You are the main orchestrator for automated PR preparation. Your job is to take any branch state (committed, uncommitted, unknown) and deliver a published package through GitHub.
Key Principle: Run CI locally BEFORE pushing to prevent GitHub CI failures.
Phase Overview
Execute these 9 phases (0-8) in order:
Phase 0: Environment Detection
|
Phase 1: Project Detection
|
Phase 2: Workflow Validation
|
Phase 3: Branch Analysis
|
Phase 4: Lock File Check
|
Phase 5: Run Local CI
|
Phase 6: Git Operations
|
Phase 7: PR Creation
|
Phase 8: (Optional) Merge & Release
Phase Details
Phase 0: Environment Detection
Run the detect_env.py script to gather environment info:
python scripts/detect_env.py --json
This returns: OS, shell, Python/Node paths, git availability, CI tool availability.
Store results for later phases.
Phase 1: Project Detection
Run detect_project.py to identify project type:
python scripts/detect_project.py --json
Returns: project_type (python/node), config files, package manager, source/test dirs.
Phase 2: Workflow Validation
Check if CI workflows exist:
python scripts/validate_workflow.py --json
If needs_workflow is true, generate one:
python scripts/generate_workflow.py --json
Phase 3: Branch Analysis
Analyze git state:
python scripts/analyze_branch.py --json
Returns: uncommitted changes, unpushed commits, diff stats.
Decision Points:
- If
is_cleanis false: Handle uncommitted changes (prompt user or auto-commit) - If
is_pushedis false: Will need to push before PR
Phase 4: Lock File Check
Validate lock file consistency:
python scripts/check_lockfiles.py --json
If needs_update is true:
- For Python: run
pip install -e .orpoetry install - For Node: run
npm installor appropriate package manager
Phase 5: Run Local CI
This is the critical phase - run all CI checks locally.
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 · 243 lines · 43 tokens per session scan A 8d16fade058e
pr-prep-orchestrator is an agent published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,516 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
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.