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 skills add diagrid-labs/dapr-skills --skill review-agent-orchestrationgit clone --depth 1 https://github.com/diagrid-labs/dapr-skillsWrote 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/diagrid-labs/dapr-skills/review-agent-orchestration)<a href="https://agentmods.dev/skills/diagrid-labs/dapr-skills/review-agent-orchestration"><img src="https://agentmods.dev/badge/skills/diagrid-labs/dapr-skills/review-agent-orchestration/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/diagrid-labs/dapr-skills/review-agent-orchestration"><img src="https://agentmods.dev/badge/skills/diagrid-labs/dapr-skills/review-agent-orchestration.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.00057 | $0.00609 |
| Opus 5 | $0.00028 | $0.00304 |
| Sonnet 5 | $0.00011 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
review-agent-orchestration 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 12d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Agents — Orchestration
Overview
Scans multi-agent projects (coordinator + specialists) for pub/sub topic naming conventions, loop safety (max_iterations), agent-registry wiring, port collisions in dapr.yaml, and cross-agent shared-state hazards. Read-only. Single-agent projects receive zero findings.
Execution Order
You MUST follow these phases in strict order.
- Resolve scope — Read
../shared/review-scope-prompt.mdand follow it to setscope_root. - Detect target — Read
../shared/review-detect-target-agent.md. Iftopology == single-agent, emitNo issues found.and stop. - Load checklist — Based on
language, read exactly one of: - Scan — Apply every rule. Port-collision rules require parsing
dapr.yaml; topic-routing rules require grepping forpublish_topic=/subscribe_topic=/DaprClient.PublishEventAsync(. - Report — Format findings using
../shared/review-report-format.md. - Show final message — Emit the report from step 5 with a
## Next stepsblock.
Prerequisites
- Read access to the project directory.
Allowed tools
Read, Grep, Glob only.
Rules
- Python rules —
DAG-ORCH-001…DAG-ORCH-009 - .NET rules — shared subset of
DAG-ORCH-*(see the rule-id map in the Python file)
Show final message
The last thing you emit MUST be the report from step 5. ## Next steps should suggest:
- Run
review-agent-toolsandreview-agent-memorynext if not yet run. - Run
review-agent-observabilityfor nativedapr-agentsprojects. - Re-run this skill after fixing critical findings.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 51 lines · 57 tokens per session scan A cd35688b4d39
review-agent-orchestration is a skill published in the GitHub repository diagrid-labs/dapr-skills (12 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 609 once invoked, about $0.0003 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
pull-feedback
Use when the user has authored a GitHub pull request and wants to work through review feedback on it. Triggers on phrases like "pull down the review on.
inbox
Use when checking what PRs are waiting for your review, or when starting your day to see what needs attention.
checking-for-undisclosed-context
Use when reviewing or drafting a doc, PR/issue description, design doc, code-review prompt, or subagent persona that's supposed to stand on its own, to check whether it leans on vocabulary, acronyms, or structure pulled from other documentation or conversation the reader hasn't seen. Read it cold, as the specific…
code-auditing
A code review and auditing guide with several modes for finding problems, simplifying code, or combining multiple review viewpoints. It includes instructions written partly in Chinese.
code-review-workflow
A step-by-step process for reviewing a pull request or merge request, which is a proposed code change awaiting review. It combines file and change summaries, automated checks, and architecture review.
code-review
A structured code-review guide that checks code for correctness, security, edge cases, concurrency problems, tests, and maintainability.