Agent Orchestrator is a local desktop workspace for running and supervising multiple coding agents, giving each task its own session, workspace, branch, and feedback loop. It is for developers coordinating agent fleets across repositories, pull requests, CI runs, reviews, and merges. The catalogue entries are commands, skills, and instructions for working with this orchestrator.
Borrowing it
Nothing to install: this file belongs to Untrivial-ai/agent-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Untrivial-ai/agent-orchestrator/main/.agents/skills/pr-description/SKILL.mdgit clone --depth 1 https://github.com/Untrivial-ai/agent-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/skills/untrivial-ai/agent-orchestrator/pr-description)<a href="https://agentmods.dev/skills/untrivial-ai/agent-orchestrator/pr-description"><img src="https://agentmods.dev/badge/skills/untrivial-ai/agent-orchestrator/pr-description/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/untrivial-ai/agent-orchestrator/pr-description"><img src="https://agentmods.dev/badge/skills/untrivial-ai/agent-orchestrator/pr-description.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00317 |
| Opus 5.5 | $0.00008 | $0.00127 |
| Sonnet 5.5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
pr-description 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 1mo 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
PR description
Begin every PR description with these three lines, using Markdown hard line breaks so each renders separately:
Code changes: +<added> -<deleted>
Tests: +<added> -<deleted>
Others: +<added> -<deleted>
Calculate the numbers from the net diff against the PR's actual base. For a local
branch, use git diff --numstat <base>...<head>. After pushing, prefer GitHub's
per-file additions and deletions. Recalculate after the final push rather than
summing commit churn or estimating counts.
Count every changed file exactly once:
- Code changes: handwritten implementation, including SQL, migrations, styles, and executable scripts.
- Tests: test code, fixtures, snapshots, and test-only helpers.
- Others: generated or vendored files, lockfiles, documentation, configuration, and assets. Generated output belongs here even when it contains source code.
Show +0 -0 for empty categories. Binary files have no line count; mention their
count separately when present. Add a brief qualifier when useful, such as
Others: +11 -0 (generated sqlc).
Preserve the rest of an existing PR description. After creating or updating the PR, read the published description and verify that its opening lines match the current GitHub diff counts and required order.
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.
- 1mo ago First seen · 37 lines · 21 tokens per session scan A 3b7a97e032e7
pr-description is a skill published in the GitHub repository Untrivial-ai/agent-orchestrator (13,596 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 317 once invoked, about $0.0001 per session on Opus 5.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-09-15.
Other skills, from other repositories
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
enable-review
Turn interactive commit reviews back on for the current herdr workspace.
comprehensive-review-pr-enhance
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
git-workflow
Git best practices, branching strategies, commit conventions, and code review patterns.