Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add navapbc/digital-service-orchestra/plugin install dsoWrote 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/navapbc/digital-service-orchestra/review)<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/review"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/review/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/navapbc/digital-service-orchestra/review"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/review.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.00084 | $0.00673 |
| Opus 5 | $0.00042 | $0.00336 |
| Sonnet 5 | $0.00017 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
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 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review
Shallow entry point for the DSO tiered code review workflow.
DSO_WORKFLOW=$(DSO_DEPRECATION_QUIET=1 ".claude/scripts/dso" read-config.sh dso.workflow 2>/dev/null || true)
if [ "$DSO_WORKFLOW" = "ci-pr" ]; then
.claude/scripts/dso commit-step skip reviewer-record "dso.workflow=ci-pr"
.claude/scripts/dso commit-step skip classifier-dispatch "dso.workflow=ci-pr"
echo "dso.workflow=ci-pr — /dso:review is a no-op (CI runs llm-review)."
# END the skill — return to caller. Do NOT proceed to "Instructions" below.
exit 0
fi
The rationalization "but I should run it anyway to be safe" is exactly the failure mode this gate prevents. The pre-commit review-gate and the Layer 2 hook both already skip enforcement under ci-pr; dispatching here adds latency and cost without changing the merge outcome.
What This Does
Loads and executes ${CLAUDE_PLUGIN_ROOT}/docs/workflows/REVIEW-WORKFLOW.md inline. That document is the authoritative review workflow — this skill exists only to provide a /dso:review invocation surface. All review logic, tier selection, agent dispatch, and resolution rules are in REVIEW-WORKFLOW.md.
Usage
/dso:review
Run from the orchestrator context (sprint, commit, or standalone) before committing.
Instructions
IMPORTANT: Do NOT call the Skill tool again or re-invoke /dso:review recursively. Instead:
- Read
${CLAUDE_PLUGIN_ROOT}/docs/workflows/REVIEW-WORKFLOW.mdnow. - Execute its steps verbatim — starting from Step 0 (Clear Stale Review Artifacts).
- Follow all HARD-GATE sections and workflow enforcement gates.
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 · 50 lines · 84 tokens per session scan A 08f689e73b3c
review is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 673 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…