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 agentmods add skills/solana-foundation/solana-developer-platform/sdp-tokenizationnpx skills add solana-foundation/solana-developer-platform --skill sdp-tokenizationgit clone --depth 1 https://github.com/solana-foundation/solana-developer-platformWrote 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/solana-foundation/solana-developer-platform/sdp-tokenization)<a href="https://agentmods.dev/skills/solana-foundation/solana-developer-platform/sdp-tokenization"><img src="https://agentmods.dev/badge/skills/solana-foundation/solana-developer-platform/sdp-tokenization.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00692 |
| Opus 5 | $0.00026 | $0.00346 |
| Sonnet 5 | $0.00010 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
sdp-tokenization 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 5d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDP Tokenization
Use this skill when someone wants to understand how to tokenize an asset with Solana Developer Platform, map a business requirement to the right token model, or turn that plan into an SDP integration sequence.
Scope
Stay on the supported public surface only:
- public docs under
apps/sdp-docs/content/docs/** - public API contract in
apps/sdp-api/src/openapi/**
Do not rely on hidden or internal route families.
Default workflow
- Classify the asset and control model.
- Load only the relevant public references from
references/tokenization-map.md. - Recommend the right SDP template or custom configuration.
- Explain the implementation sequence in order:
- organization and wallet setup
- API key scope and permissions
- token creation
- deployment
- minting, transfers, and redemptions
- allowlist, freeze, pause, and authority operations if needed
- Call out operational constraints and authority ownership explicitly.
Output shape
Default to these sections unless the user asks for something narrower:
- Asset type and operating model
- Recommended SDP template or token configuration
- Required wallets, authorities, and permissions
- Step-by-step implementation flow
- Relevant docs and endpoints
- Risks, compliance controls, and operational caveats
Decision rules
- Recommend
stablecoinfor fiat-backed issuance with pause and delegated admin controls. - Recommend
tokenized-securityfor regulated assets that usually need allowlists and stronger compliance controls. - Recommend
arcadefor closed-loop, loyalty, or gaming-style tokens. - Recommend
customonly when templates do not fit the issuance model. - Prefer SDP-controlled custody wallets for mint, freeze, metadata, and other authorities by default.
- Treat external or multisig authorities as an advanced path and state that clearly.
Operational guidance
- A token must be created before it can be deployed, and deployed before it can be minted or transferred.
- Amounts are usually submitted in smallest-unit token amounts, not UI-decimal strings.
- Burn, freeze, and similar account-level operations often require a token account address rather than a wallet address.
- If a token is paused, minting and transfer-related actions should be treated as unavailable until it is unpaused.
- If a workflow needs SDP to sign directly, recommend execute flows first; use prepare flows only when the signer needs to be external to SDP.
What ships with it
2 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.
- 5d ago First seen · 72 lines · 52 tokens per session scan A 7a56d78f9d97
sdp-tokenization is a skill published in the GitHub repository solana-foundation/solana-developer-platform (49 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 692 once invoked, about $0.0003 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-30.
Other skills, from other repositories
official-sui-skills
Pointer to the official Mysten Labs skills for building on Sui — language fundamentals, object model, PTBs, SDKs, publishing, upgrades, frontend integration, accessing on-chain data. Maintained upstream at github.com/MystenLabs/skills; pinned to the same ref the audit catalog derives from (see…
nip85-trusted-assertions
The NIP-85 trusted-assertions model in Quartz (nip85TrustedAssertions/) — kind 10040 trust-provider lists, kind 30382 contact cards / user assertions, 30383 event assertions, 30384 addressable assertions, 30385 external-id assertions. Use when building or parsing these events, working with the typed tags (RankTag…
bridge
Cross-chain token transfers using Wormhole and CCTP.
onchainkit
Build onchain apps with Coinbase's OnchainKit React components - wallets, swaps, NFTs, payments.
marginfi
MarginFi — Solana lending and borrowing.
sparkbtcbot-proxy-deploy
Deploy a serverless Spark Bitcoin L2 proxy on Vercel with spending limits, auth, and Redis logging. Use when user wants to set up a new proxy, configure env vars, deploy to Vercel, or manage the proxy infrastructure.