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 x402agent/solana-clawd --skill pump-solana-architecturegit clone --depth 1 https://github.com/x402agent/solana-clawdWrote 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/x402agent/solana-clawd/pump-solana-architecture)<a href="https://agentmods.dev/skills/x402agent/solana-clawd/pump-solana-architecture"><img src="https://agentmods.dev/badge/skills/x402agent/solana-clawd/pump-solana-architecture/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/x402agent/solana-clawd/pump-solana-architecture"><img src="https://agentmods.dev/badge/skills/x402agent/solana-clawd/pump-solana-architecture.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.00048 | $0.01043 |
| Opus 5 | $0.00024 | $0.00522 |
| Sonnet 5 | $0.00010 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
pump-solana-architecture 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana Program Architecture — PDAs, Accounts & Multi-Program Coordination
Design, derive, and manage Program Derived Addresses (PDAs) and account layouts across the Pump ecosystem's four Solana programs with cross-program invocation patterns.
On-Chain Programs
| Program | ID | Purpose |
|---|---|---|
| Pump | 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P |
Bonding curve operations |
| PumpAMM | pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA |
Graduated AMM pools |
| PumpFees | pfeeUxB6jkeY1Hxd7CsFCAjcbHA9rWtchMGdZ6VojVZ |
Fee sharing |
| Mayhem | MAyhSmzXzV1pTf7LsNkrNwkWKTo4ougAJ1PPg47MD4e |
Mayhem-mode tokens |
PDA Categories
Global Singletons
GLOBAL_PDA—["global"]on Pump — protocol-wide configFEE_CONFIG_PDA—["fee-config"]on Pump — tiered fee settingsGLOBAL_VOLUME_ACCUMULATOR_PDA—["global_volume_accumulator"]— protocol-wide volume
Per-Token PDAs
bondingCurvePda(mint)—["bonding-curve", mint]— token bonding curve statebondingCurveTokenAccountPda(mint)—["bonding-curve-token-account", mint]feeSharingConfigPda(mint)—["sharing-config", mint]on PumpFeescanonicalPumpPoolPda(mint)— AMM pool for graduated token
Per-User PDAs
creatorVaultPda(creator)—["creator-vault", creator]on PumpammCreatorVaultPda(creator)—["creator_vault", creator]on PumpAMMuserVolumeAccumulatorPda(user)—["user_volume_accumulator", user]
Mayhem PDAs
mayhemMetadataPda(mint)—["mayhem_metadata", mint]on MayhemmayhemWsolPda()—["mayhem_wsol"]on Mayhem
BothPrograms Pattern
Many operations span both Pump and PumpAMM — the SDK provides aggregation:
| Method | Description |
|---|---|
getCreatorVaultBalanceBothPrograms |
Sum balance from both vaults |
collectCoinCreatorFeeInstructions |
Collect from both programs |
fetchUserVolumeAccumulatorTotalStats |
Aggregate volume across programs |
claimTokenIncentivesBothPrograms |
Claim rewards from both |
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.
- 7d ago First seen · 94 lines · 48 tokens per session scan A 899f36a3a1e7
pump-solana-architecture is a skill published in the GitHub repository x402agent/solana-clawd (24 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,043 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-09-03.
Other skills, from other repositories
web3-fullstack-packaged-build
Systematic full-stack Web3 build with mandatory packaging and delivery phase.
web3-fullstack-systematic-build
Systematic approach to building full-stack Web3 applications layer by layer.
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain…
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
walkeros-create-destination
Use when creating a new walkerOS destination to send events to a vendor or API (GA4/gtag, Meta/Facebook Pixel, Mixpanel, Amplitude, a custom HTTP API, Measurement Protocol), web or server-side. Example-driven workflow: research the vendor SDK and define step examples before implementing the destination interface, env…
walkeros-create-source
Use when creating a new walkerOS source to capture events (browser source, dataLayer interception, server/HTTP source, webhook receiver, event capture), web or server-side. Example-driven workflow: research the input format and define step examples before implementing the push interface, createTrigger, and env pattern.