sap-agent-registry

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

A set of tools for managing SAP agent identities and profiles. An agent registry is a directory that records agents, their profiles, and whether they are active.

In plain words
What is it for?
Registering agents, updating profiles or images, checking activation and statistics, linking identities, and listing or discovering agents.
Why use it?
It helps plan and validate identity changes before registration or profile updates, and supports targeted directory lookups.

Skill for Claude CodeCodex

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

Good fit Registering agents, updating profiles or images, checking activation and statistics, linking identities, and listing or discovering agents.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/oobe-protocol/sap-mcp/sap-agent-registry"><img src="https://agentmods.dev/badge/skills/oobe-protocol/sap-mcp/sap-agent-registry.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 1,652 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.01652
Opus 5 $0.00000 $0.00826
Sonnet 5 $0.00000 $0.00330
Haiku 4.5 $0.00000 $0.00165

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

Security

Grade A, and why

sap-agent-registry 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-agent-registry/SKILL.md · 135 lines

How it starts

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

SAP Agent Registry

Use this skill for SAP agent identity, registration, profile updates, activation state, global directory listing, and agent profile inspection.

First Steps

  1. Call sap_profile_current.
  2. Call sap_protocol_invariants before registry writes when treasury, fee, hosted/local routing, or lifecycle-complete rules are unclear.
  3. For registration, profile-image updates, Metaplex identity, SNS linking, or full identity setup, call sap_agent_identity_plan before any write. It is free and returns normalized fields, local-signer routing, metadata contract, forbidden actions, and verification checklist.
  4. Use low-cost exact/base micro-reads before broad discovery: sap_agent_context, sap_get_agent, sap_get_agent_profile, sap_get_agent_stats, sap_is_agent_active, sap_get_global_state, and sap_list_agents with limit <= 20, view: "compact", and includeProtocolIndexes: false.
  5. Call sap_get_network_overview for ecosystem counters when needed.
  6. Use sap_discover_agents with query, wallet, protocol, or capability for targeted read-premium hosted directory reads when micro-read reads are not enough.
  7. Use sap_list_all_agents for global current agent lists and follow pagination.nextCursor for additional pages.

Tools

  • sap_register_agent
  • sap_protocol_invariants
  • sap_agent_identity_plan
  • sap_agent_context
  • sap_agent_next_action
  • sap_update_agent
  • sap_deactivate_agent
  • sap_reactivate_agent
  • sap_close_agent
  • sap_get_agent
  • sap_get_agent_profile
  • sap_get_agent_stats
  • sap_get_global_state
  • sap_get_network_overview
  • sap_list_agents
  • sap_list_all_agents
  • sap_is_agent_active
  • sap_report_calls
  • sap_update_reputation_metrics

Routing

  • Hosted accountless SAP MCP cannot sign user-owned registry writes. If sap_register_agent, sap_update_agent, or another registry write returns hosted_local_signer_required, no x402 payment was charged. For agent registration, call the local sap_payments.sap_payments_register_agent bridge with the same fields and confirm: true; it signs locally with the active SAP MCP profile. For agent profile, image, metadata, capability, protocol, pricing, or x402 endpoint updates, call local sap_payments.sap_payments_update_agent with the same update fields and confirm: true. For other registry writes, run the write on the local SAP MCP profile or use a production unsigned builder/finalizer flow when available.
  • Before any retry after payment_required, hosted_local_signer_required, BlockhashNotFound, timeout, missing sap_payments, or a submitted signature that did not confirm, call sap_agent_next_action. Follow its safeToRetryNow, nextTool, and forbiddenActions fields.
  • Agent pictures must be public metadata, not desktop file paths. Upload the image or metadata JSON to IPFS, Arweave, Kommodo, or HTTPS, then set agentUri/metadataUri with sap_payments_update_agent.
  • After sap_payments_register_agent, do not stop at a Solscan link. Verify success, agentRegistered, agentPda, confirmationStatus, protocolComplete, and protocolFee.status. A complete registration should show the expected protocol fee credited to treasury J7PyZAGKvprCz4SQ5DKBLAHstJxgVqZcz6kguUoWpP7P. If success is false but agentRegistered is true, the account may exist but SAP registration is not protocol-complete. Report the integrity issue and do not retry automatically.
  • After sap_payments_update_agent, fetch the agent profile again and verify the changed fields. For image/profile updates, agentUri or metadataUri must resolve to public metadata containing the image URL.
  • If sap_payments_update_agent returns Anchor 3012, AccountNotInitialized, or mentions pricing_menu, do not run runtime repair and do not retry the same write. This means the write reached the SAP on-chain program but a required registry lifecycle PDA is missing or stale. Call sap_agent_next_action and sap_protocol_invariants, then upgrade the SDK/server or use the initializer path before retrying.
  • For full agent identity setup, follow docs/16_AGENT_IDENTITY_REGISTRY_PIPELINE.md: SAP registration first, optional Metaplex/MPL Core identity, optional SNS domain and records, then a final SAP update that points metadataUri at the public metadata document.
  • "Find XONA Agent" or "find an agent by name" means sap_discover_agents with query.
  • "Find x402 agents" means sap_discover_agents with hasX402Endpoint: true.
  • "List all agents" means first call free sap_list_agents with limit <= 20, view: "compact", and includeProtocolIndexes: false; then use paid sap_list_all_agents with pagination.nextCursor if the user wants more, full rows, or ecosystem-scale enumeration.
  • "Agent by wallet" means sap_get_agent or sap_get_agent_profile.
  • "Is this agent live?" means sap_is_agent_active.
  • "Network totals" means sap_get_network_overview.

Read the full file on GitHub · 135 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 · 135 lines · 0 tokens per session scan A 6c48a2403bce

Subscribe to this mod's changes

sap-agent-registry 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 1,652 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens