sap-escrow-settlement

sap-escrow-settlement is a skill for Claude Code, Codex from OOBE-PROTOCOL/sap-mcp. It costs 0 tokens per session (546 once invoked), scanned A, original, MIT.

A set of tools for active Escrow V2 agreements, which hold funds until agreed settlement steps are completed. It also handles withdrawals, closing, pending settlements, and disputes.

In plain words
What is it for?
Creating and funding escrows, settling or finalizing them, withdrawing or closing funds, checking their state, and filing disputes.
Why use it?
It helps manage escrow payments using the current version of the on-chain program and avoids inactive V1 write operations.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Creating and funding escrows, settling or finalizing them, withdrawing or closing funds, checking their state, and filing disputes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oobe-protocol/sap-mcp/sap-escrow-settlement
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.

Any agent
npx skills add OOBE-PROTOCOL/sap-mcp --skill sap-escrow-settlement
Clone the repo
git clone --depth 1 https://github.com/OOBE-PROTOCOL/sap-mcp

Made for: Claude Code, Codex.

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 sap-escrow-settlement

README.md
[![agentmods](https://agentmods.dev/badge/skills/oobe-protocol/sap-mcp/sap-escrow-settlement/github.svg)](https://agentmods.dev/skills/oobe-protocol/sap-mcp/sap-escrow-settlement)
Your own site
<a href="https://agentmods.dev/skills/oobe-protocol/sap-mcp/sap-escrow-settlement"><img src="https://agentmods.dev/badge/skills/oobe-protocol/sap-mcp/sap-escrow-settlement/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 sap-escrow-settlement

Your own site · 80×15
<a href="https://agentmods.dev/skills/oobe-protocol/sap-mcp/sap-escrow-settlement"><img src="https://agentmods.dev/badge/skills/oobe-protocol/sap-mcp/sap-escrow-settlement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 546 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.00000 $0.00546
Opus 5 $0.00000 $0.00273
Sonnet 5 $0.00000 $0.00109
Haiku 4.5 $0.00000 $0.00055

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

Security

Grade A, and why

sap-escrow-settlement 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 9d 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.

skills/sap-escrow-settlement/SKILL.md · 60 lines

How it starts

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

SAP Escrow Settlement

Use this skill for active Escrow V2 deposits, settlement, withdrawal, closing, pending settlements, and disputes. V1 escrow write flows are no longer active on the current SAP on-chain program and must not be used for new work.

Tools

Hosted unsigned builders:

  • sap_escrow_build_create_transaction
  • sap_escrow_build_deposit_transaction
  • sap_escrow_build_settle_transaction
  • sap_escrow_build_finalize_transaction
  • sap_escrow_build_withdraw_transaction
  • sap_escrow_build_close_transaction

Local-signer direct writes:

  • sap_create_escrow_v2
  • sap_deposit_escrow_v2
  • sap_settle_escrow_v2
  • sap_finalize_settlement_v2
  • sap_file_dispute_v2
  • sap_withdraw_escrow_v2
  • sap_close_escrow_v2
  • sap_fetch_escrow_v2
  • sap_fetch_pending_settlement
  • sap_next_settlement_index
  • sap_fetch_dispute
  • sap_fetch_escrow

sap_fetch_escrow is retained only for legacy read-only inspection. Do not recommend V1 create, deposit, settle, withdraw, close, or batch-settle flows.

Flow

  1. Fetch V2 escrow state before mutating it.
  2. In hosted SAP MCP, never call direct escrow write tools after hosted_local_signer_required. Use the matching sap_escrow_build_*_transaction tool, then finalize the unsigned transaction locally with sap_payments_finalize_transaction.
  3. In local SAP MCP stdio mode, direct write tools can sign through the active local SAP profile. Do not read keypair JSON or create temporary signing scripts.
  4. For V2 settlement, inspect pending settlement and dispute state.
  5. Explain amount, depositor, agent PDA, nonce, settlement index, and dispute effect before write tools.
  6. Treat settlementSecurity = 2 / DisputeWindow as the safe default. Use settlementSecurity = 1 / CoSigned only when a valid coSigner is provided. Never default to SelfReport / 0.
  7. Amounts are always in the smallest unit of the escrow token: lamports for SOL, micro-USDC for USDC.

Safety

Escrow tools can lock, move, or release funds. Use preview/signing policy and explicit user approval for high-value actions.

Read the full file on GitHub · 60 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. 9d ago First seen · 60 lines · 0 tokens per session scan A 9d972ae91e5a

Subscribe to this mod's changes

sap-escrow-settlement is a skill published in the GitHub repository OOBE-PROTOCOL/sap-mcp (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 546 tokens. 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.