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.
git clone --depth 1 https://github.com/navapbc/digital-service-orchestraWrote 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/navapbc/digital-service-orchestra/scope-drift-reviewer)<a href="https://agentmods.dev/agents/navapbc/digital-service-orchestra/scope-drift-reviewer"><img src="https://agentmods.dev/badge/agents/navapbc/digital-service-orchestra/scope-drift-reviewer/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/agents/navapbc/digital-service-orchestra/scope-drift-reviewer"><img src="https://agentmods.dev/badge/agents/navapbc/digital-service-orchestra/scope-drift-reviewer.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.00058 | $0.02595 |
| Opus 5.5 | $0.00023 | $0.01038 |
| Sonnet 5.5 | $0.00012 | $0.00519 |
| Haiku 4.5 | $0.00006 | $0.00260 |
Grade C, and why
scope-drift-reviewer scanned grade C with 2 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 2mo 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- REVIEW-DEFENSE: The agent name "scope-drift-reviewer" (without "dso:" prefix) is CORRECT. The Claude Code plugin framework automatically adds the "dso:" namespace prefix to all agent name fields at registration time Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. New external service calls: `gh issue create`, `gh api POST/PUT/PATCH`, `gh pr comment`, `requests.post()`, `curl -X POST` — calls that create or mutate resources in external systems How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Drift Reviewer Agent
You are a post-fix scope-drift classifier for the /dso:fix-bug workflow. Your sole purpose is to classify whether the changes in git_diff stay within the behavioral scope described in ticket_text, or whether they introduce behavioral changes outside that boundary. You emit a gate signal JSON object conforming to the gate-signal-schema.md contract.
Dispatch Parameters
The caller passes these parameters in the dispatch prompt:
ticket_text— The full bug ticket text (title, description, acceptance criteria)root_cause_report— Investigation findings from the fix-bug workflow (root cause, hypothesis tests, fix rationale)git_diff— The unified diff of all changes introduced by the fix
PARSED_SCOPE Checkpoint
Do NOT read root_cause_report before PARSED_SCOPE block is complete.
Before examining any other input, parse ticket_text and emit a PARSED_SCOPE block:
PARSED_SCOPE:
stated_behavior_change: <single sentence — what the ticket says should change>
affected_component: <file, module, or subsystem named in ticket>
scope_boundary: <what the ticket explicitly limits or excludes, if stated>
scope_confidence: <high | medium | low>
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.
- 2mo ago First seen · 209 lines · 58 tokens per session scan C 9487dff98d80
scope-drift-reviewer is an agent published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 2,595 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (hidden instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
scope-drift-reviewer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| scope-drift-reviewernavapbc/digital-service-orchestra | Agent | 6 | yesterday | Apache-2.0 | C | 58 | Claude Code |
| cpp-revieweraffaan-m/ECC | Agent | 301k | 2d ago | MIT | A | 41 | Claude Code, Kiro |
| thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claude | Agent | 4.2k | today | MIT | A | 68 | Claude Code |
| review-obsidian-guidelinesuphy/obsidian-reminder | Agent | 662 | 6d ago | MIT | A | 63 | Claude Code |
| atomic-auditordamusix/atomic-claude | Agent | 116 | yesterday | MIT | A | 169 | Claude Code |
| karimo-implementeropensesh/KARIMO | Agent | 291 | 29d ago | Apache-2.0 | A | 49 | Claude Code |
| reviewergenkovich/sdd | Agent | 202 | 27d ago | MIT | A | 81 | Claude Code |