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.
npx skills add trilltino/solana_coralOS --skill solana-agent-commercegit clone --depth 1 https://github.com/trilltino/solana_coralOSWrote 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.
[](https://agentmods.dev/skills/trilltino/solana_coralos/solana-agent-commerce)<a href="https://agentmods.dev/skills/trilltino/solana_coralos/solana-agent-commerce"><img src="https://agentmods.dev/badge/skills/trilltino/solana_coralos/solana-agent-commerce/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.
<a href="https://agentmods.dev/skills/trilltino/solana_coralos/solana-agent-commerce"><img src="https://agentmods.dev/badge/skills/trilltino/solana_coralos/solana-agent-commerce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.01573 |
| Opus 5 | $0.00017 | $0.00787 |
| Sonnet 5 | $0.00007 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
solana-agent-commerce 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana Agent Commerce Skill
Use this skill when a builder asks to add or change a paid autonomous service in this repo.
Mental Model
The core CoralOS round (coral-agents/buyer-agent, coral-agents/seller-agent, coral-agents/verifier-agent) runs this exact wire sequence — every verb below is a real message posted on the market thread, not an aspirational diagram:
WANT -> BID -> AWARD -> PAYMENT_REQUIRED -> PAYMENT_PROOF -> PAYMENT_CONFIRMED -> DELIVERED -> VERIFY -> VERIFIED -> SETTLED
Settlement is x402: the buyer pays the seller directly and finally, before delivery. There is no
escrow in this path — a seller that takes payment and never delivers keeps it; reputation is the
defense, not a refund. Escrow/arbiter Anchor programs still exist and are deployed
(examples/txodds/escrow), available as an alternative building block, but coral-agents does not
use them — don't describe the core round in terms of ESCROW_REQUIRED/DEPOSITED/RELEASED, those
message types no longer exist in protocol.ts.
All the round's messages are typed (format*/parse* pairs) in packages/agent-runtime/src/market/protocol.ts:
- Core round messages:
WANT,BID,AWARD,VERIFY,VERIFIED. - Payment messages (rail-generic, but this is where the primary settlement lives now):
PAYMENT_REQUIRED/PAYMENT_PROOF/PAYMENT_CONFIRMED/SETTLED/REFUNDED. The seller's AWARD reply always usesrail=x402for the round's primary payment; the SAME message types, with a differentreference, also carry the seller's optional upstream-procurement leg (PROCURE_RAIL=x402,packages/payment-runtime/src/procure.ts) — the firstPAYMENT_REQUIREDin a round is always the primary leg. - Untyped verbs:
DELIVEREDhas no formatter/parser —seller-agent/buyer-agentbuild and match it as a plain string. Seereferences/market-protocol.mdfor exactly how.
Keep business logic separate from payment movement:
- Service delivery belongs in seller service modules or harness adapters.
- Payment selection belongs in
packages/payment-runtime. - Spend and merchant checks belong in policy modules (
packages/agent-runtime/src/policy/policy.ts). - Wire-format changes belong in
packages/agent-runtime/src/market/protocol.ts. - Auditable proof belongs in the run ledger (
packages/agent-runtime/src/ledger/).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 70 lines · 34 tokens per session scan A e32bd34cbac6
solana-agent-commerce is a skill published in the GitHub repository trilltino/solana_coralOS (5 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,573 once invoked, about $0.0002 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.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
agentic-commerce-forthecult
Agentic Commerce skills enables agents to autonomously browse and search for quality lifestyle, wellness, and tech products and gifts, view details, create orders with multi-chain payments (Solana, Ethereum, Base, Polygon, Arbitrum, Bitcoin, Dogecoin, Monero), apply CULT token-holder discounts, and track orders from…
dutch-auction-patterns
Use when implementing Dutch auctions for token sales, NFT mints, fair launch mechanisms, or Gradual Dutch Auctions (GDAs). Covers linear/exponential price decay, batch auctions, and MEV-resistant patterns.
moonpay-commerce
Browse Shopify stores, search products, manage a cart, and checkout with crypto via Solana Pay. No login required.
opensea
Query OpenSea marketplace data — listings, offers, sales / events, floor prices, collection stats, drops, traits — and execute Seaport trades via the official @opensea/cli and OpenSea REST API across Ethereum, Base, Arbitrum, Optimism, Polygon, and more. Includes search across collections / NFTs / tokens / accounts.…