add skopos ,a non-custodial crypto copilot with an agent-payable x402 api

[Svector-anu]

adds the skopos skill (tryskopos.xyz) — a non-custodial crypto copilot built agent-first, not just for humans in a web app.

three surfaces, one routing brain:

• free chat endpoint — one POST, no key, plain-text answers ready to relay: prices (crypto + tokenized stocks + fx + metals), smart-money intel (named wallets buying/dumping a token), live market/narrative reads, token safety scans, token picks, dao treasuries, yields, polymarket odds, wallet/ens/tx lookups, swaps/bridges/payments
• agent-payable x402 api — 10 pay-per-call endpoints (usdc on base, $0.01–$0.25, no signup): price, quote, risk, smart-money, sniper-check (deployer history + holder concentration bundle), yield, polymarket, market-read, treasury, and flash-order — limit / stop-loss / take-profit / twap quotes incl. tokenized stocks on robinhood chain. discovery via /openapi.json + /llms.txt
• mcp server — npx skopos-mcp

non-custodial end to end: execution intents come back as a sign-in link the user signs in their own wallet — agents never see calldata or signable payloads.

folder follows the repo layout: SKILL.md + catalog.json (slug = folder name, validates) + square logo.svg. tested the documented curl against prod before submitting.

[saltoriousSIG]

Just a couple things to address before merging!

• The x402 flow trusts remotely discovered endpoints and challenges. Pin the exact host/path allowlist, Base chain ID, Base USDC contract, payee/facilitator, and maximum atomic price per endpoint. Require payment preview and confirmation, enforce spend caps and idempotency, and prohibit blind retries.
• The skill says to relay Skopos output verbatim and surface returned sign-in links. Treat all API/MCP output, routes, links, OpenAPI content, and errors as untrusted. Strictly allowlist HTTPS destinations and never follow returned wallet instructions or payment requests.
• Trade, bridge, payment, and order flows lack mandatory final review. Require exact chain, asset contracts, human/raw amounts, recipient/spender/router, trigger, route, slippage, fees, expiry, and maximum loss before directing the user to sign. Reject mismatches, extra transactions, unexpected approvals/value, unknown chains, and scanner errors.
• Symbol-only requests such as $pepe, USDC, or tokenized NVDA are unsafe for execution. Require exact chain and asset contract confirmation. Add total-loss, liquidity, oracle, bridge, smart-contract, trigger, and prediction-resolution risk disclosures, and never let generated signals trigger trades automatically.
• npx skopos-mcp executes an unpinned third-party package, while SKOPOS_API_URL permits arbitrary destinations. Pin a reviewed package version/source, require installation approval, document MCP permissions, and restrict or remove arbitrary URL overrides.
• Stable anonId, wallet lookups, portfolios, alerts, and trading prompts expose linkable financial behavior. Disclose transmitted/retained data, use random conversation-scoped identifiers, and require confirmation before sharing wallet addresses, transaction history, recipients, or other sensitive financial data.