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.
npx agentmods add skills/drvoss/everything-copilot-cli/pr-multi-perspective-reviewnpx skills add drvoss/everything-copilot-cli --skill pr-multi-perspective-reviewgit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/pr-multi-perspective-review)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/pr-multi-perspective-review"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/pr-multi-perspective-review.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 | $0.00035 | $0.02364 |
| Opus 5 | $0.00017 | $0.01182 |
| Sonnet 5 | $0.00007 | $0.00473 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
pr-multi-perspective-review 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 4d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Multi-Perspective Review
When to Use
- Before merging any significant PR — to catch issues a single reviewer might miss
- When the PR touches multiple concerns (UI + API + infra all at once)
- For PRs with external impact: public API changes, auth logic, billing flows
- As a pre-merge gate in high-stakes or regulated environments
Differentiation from code-review: code-review is a single technical pass.
This skill runs 6 distinct lenses simultaneously, surfacing business, quality, and
operational issues that a developer reviewer alone would not flag.
Prerequisites
- PR is open and has a diff available (via
ghCLI or GitHub MCP) - At minimum: PR description exists (even if brief)
Workflow
Option A — Single Session (Sequential, Lower Token Cost)
Suitable for smaller PRs or when fleet is not available.
# Fetch the PR diff
$pr = 123
gh pr diff $pr
# Fetch PR description and metadata
gh pr view $pr --json title,body,labels,additions,deletions,changedFiles
Then work through each perspective in the same session using the prompts below.
Option B — Fleet Parallel (6 Concurrent Agents, Faster)
Use fleet mode to run all 6 perspectives simultaneously:
> /fleet Run a 6-perspective review of PR #123 in owner/repo.
> Launch 6 parallel agents, each with a different lens:
> 1. PM lens: business value, scope, requirements alignment
> 2. Dev lens: code quality, architecture, maintainability
> 3. QA lens: test coverage, edge cases, regression risk
> 4. Security lens: vulnerabilities, secrets, auth, input validation
> 5. DevOps lens: CI/CD impact, performance, observability, rollback
> 6. UX lens: user-facing changes, error messages, accessibility
> 7. Optional Staff lens: system-level risk, rollout readiness, ownership burden
> Each agent should output: [PASS/CONCERN/BLOCK] + findings as bullet list.
> Final agent: synthesize all active lens outputs into a single review comment.
The 6 Perspectives
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.
- 4d ago First seen · 287 lines · 35 tokens per session scan A f5cc658be864
pr-multi-perspective-review is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 2,364 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-30.
Other skills, from other repositories
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-code-review
Code quality review for WinUI 3 apps — MVVM compliance, x:Bind correctness, accessibility, theming, security, and performance. Use before committing to catch issues that the compiler and UI tests won't find.
building-shadcn-flutter-ui
Build beautiful, accessible, and highly customizable user interfaces in Flutter using the Shadcn UI design system. This skill ensures proper framework integration (Pure, Material, or Cupertino), consistent theming, and effective use of the 30+ responsive components available in the library.
quizzing
Consolidated design questionnaire — get a design right on the first go by front-loading clarifying questions into one convenient web form instead of a long back-and-forth. The inverse (in cadence) of "grilling": first look up facts, ask 1-5 grilling-style "bearing" questions one at a time, then generate a capped (20…
github-brand
Apply GitHub-inspired brand guidance to workshop experiences using measurable visual, editorial, accessibility, and trademark rules. Use when generating or reviewing workshop pages, screens, modules, exercises, diagrams, or presentation-like workshop surfaces. This skill defines brand outcomes and…
hallmark
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.