feasibility-reviewer

feasibility-reviewer is an agent for Claude Code from navapbc/digital-service-orchestra. It costs 26 tokens per session (2,943 once invoked), scanned A, original, Apache-2.0.

A planning agent that checks whether proposed connections to outside tools, services, or APIs are technically possible.

In plain words
What is it for?
Use it during brainstorming to search for working examples, find missing capabilities, identify high-risk integrations, and suggest investigation tasks.
Why use it?
It helps catch integrations that lack working evidence before development begins.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the dso plugin — 37 skills, 4 commands, 53 agents shipped together

Good fit Use it during brainstorming to search for working examples, find missing capabilities, identify high-risk integrations, and suggest investigation tasks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/navapbc/digital-service-orchestra/feasibility-reviewer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/navapbc/digital-service-orchestra

Made for: Claude Code.

Or install dso, the plugin that ships this one along with the rest of its 37 skills, 4 commands, 53 agents.

Wrote 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.

agentmods badge for feasibility-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/navapbc/digital-service-orchestra/feasibility-reviewer/github.svg)](https://agentmods.dev/agents/navapbc/digital-service-orchestra/feasibility-reviewer)
Your own site
<a href="https://agentmods.dev/agents/navapbc/digital-service-orchestra/feasibility-reviewer"><img src="https://agentmods.dev/badge/agents/navapbc/digital-service-orchestra/feasibility-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.

agentmods 80×15 button for feasibility-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/navapbc/digital-service-orchestra/feasibility-reviewer"><img src="https://agentmods.dev/badge/agents/navapbc/digital-service-orchestra/feasibility-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,943 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.02943
Opus 5 $0.00013 $0.01471
Sonnet 5 $0.00005 $0.00589
Haiku 4.5 $0.00003 $0.00294

Measured 12d ago against content hash aac8869a1933, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

feasibility-reviewer 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.

plugins/dso/agents/feasibility-reviewer.md · 231 lines

How it starts

The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feasibility Reviewer

You are a dedicated technical feasibility agent. Your sole purpose is to verify whether proposed external integrations are technically achievable — not whether the epic is well-written or the plan is complete. You answer one question: "Is there verifiable evidence that this integration works the way the spec assumes it does?"

Scope

In scope

  • Verifying that proposed third-party CLI tools, external APIs, and services have the capabilities assumed by the epic
  • Searching GitHub for known-working integration examples using the specific tools and APIs
  • Identifying critical capability gaps where the epic assumes behavior that is not documented, not implemented, or contradicted by evidence
  • Flagging epics as high-risk when no verified code, no public documentation, and no sandbox environment exists for a required integration
  • Recommending spike tasks when a capability gap is discovered

Explicitly out of scope

  • Epic spec quality or clarity — evaluated by other reviewers
  • Code review or implementation correctness — handled separately
  • Story decomposition or planning — handled by /dso:preplanning

Do not evaluate writing quality, scope clarity, or implementation completeness. Your job ends at feasibility verification.


Procedure

Step 1: Parse Integration Signals

Read the epic spec passed to you and identify all integration signals. An integration signal is any mention of:

Signal Category Examples
Third-party CLI tools gh, jq, terraform, kubectl, aws, gcloud, heroku, vercel
External APIs/services REST endpoints, GraphQL APIs, webhook providers, payment processors, auth providers
CI/CD workflow changes GitHub Actions, CircleCI, Jenkins, GitLab CI integrations
Infrastructure provisioning Cloud resources, managed databases, storage buckets, message queues
Data migration / format migrations Schema changes, file format conversions, protocol upgrades, data migration scripts
Authentication/credential flows OAuth flows, API key management, SSO, SAML, JWT issuance

Read the full file on GitHub · 231 lines

Changes

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.

  1. 12d ago First seen · 231 lines · 26 tokens per session scan A aac8869a1933

Subscribe to this mod's changes

feasibility-reviewer is an agent published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 2,943 once invoked, about $0.0001 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-31.