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.
/plugin marketplace add SELAT-AI/selat-pluginsnpx agentmods add plugins/selat-ai/selat-plugins/selatgit clone --depth 1 https://github.com/SELAT-AI/selat-pluginsGrade A, and why
selat 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 2d 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.
What it actually says
{
"name": "selat",
"version": "0.1.9",
"description": "Discover and call paid AI capabilities via a two-tier loop \u2014 vetted multi-step skills first, then a federated x402 / MPP endpoint catalog (image/video/audio generation, translation, web scraping, data enrichment, real-time data, on-chain actions). Payments settle from your own Circle Agent Wallet (MPC self-custody \u2014 SELAT never holds your keys or funds). Wraps the published @selat-ai/selat-cli (bundles @selat-ai/selat-discovery + @selat-ai/selat-pay) and ships the 'selat-discovery' driver skill.",
"author": {
"name": "SELAT",
"url": "https://selat.ai"
},
"homepage": "https://selat.ai",
"repository": "https://github.com/SELAT-AI/selat-plugins",
"license": "Apache-2.0",
"keywords": [
"selat",
"x402",
"mpp",
"circle",
"payments",
"self-custody",
"capabilities",
"agent-tools"
]
}
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.
- 2d ago First seen · 23 lines scan A ed9a28e82ea2
selat is a plugin published in the GitHub repository SELAT-AI/selat-plugins (1 stars, last pushed 3d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
swarmwage
Hire other AI agents from inside Claude Code. Discover, hire, and pay specialized agents in USDC on Base via the open Swarmwage protocol — sub-second sync calls, on-chain receipts, zero protocol fee. Ships an MCP server plus two skills (buyer-side hire + seller-side publish).
internet-court-skill
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
internet-court-skill marketplace
Internet Court — the trust layer for agent-to-agent commerce.
t2000-skills marketplace
Plugin marketplace listing 1 plugin: t2000-agent-wallet.
a2a-multi-agent
Expert A2A (Agent-to-Agent) protocol knowledge for building multi-agent systems — Agent Cards, task lifecycle, streaming, push notifications, authentication, and framework integrations.
acp-agentic-commerce
Expert subagent and skills for implementing the Agentic Commerce Protocol (ACP) — the open standard by OpenAI and Stripe for AI-agent-mediated commerce.