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-build-releasegit 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-build-release)<a href="https://agentmods.dev/skills/x402agent/solana-clawd/pump-build-release"><img src="https://agentmods.dev/badge/skills/x402agent/solana-clawd/pump-build-release/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-build-release"><img src="https://agentmods.dev/badge/skills/x402agent/solana-clawd/pump-build-release.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.00049 | $0.00651 |
| Opus 5 | $0.00024 | $0.00326 |
| Sonnet 5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
pump-build-release 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build & Release — SDK Build Pipeline & Publishing
Build and release the Pump SDK ecosystem: tsup TypeScript builds, Cargo release profiles, semantic release, npm publishing, and deployment.
SDK Build Pipeline (TypeScript)
npx tsup src/index.ts --format cjs,esm --dts
Output: dist/index.cjs, dist/index.mjs, dist/index.d.ts
Rust Release Profile
[profile.release]
opt-level = 3
lto = true
codegen-units = 1
strip = true
Semantic Release with Commitizen
Commit format: type(scope): description
| Type | Effect |
|---|---|
feat: |
Minor version bump |
fix: |
Patch version bump |
feat!: or BREAKING CHANGE: |
Major version bump |
chore:, docs:, style: |
No release |
Makefile Targets
| Target | Description |
|---|---|
make build |
Build SDK + Rust binary |
make test |
Run all tests |
make bench |
Run benchmarks |
make lint |
Run all linters |
make clean |
Clean build artifacts |
make release |
Build release binary |
Linting
| Tool | Language | Config |
|---|---|---|
| ESLint/tsup | TypeScript | tsconfig.json |
cargo clippy |
Rust | Default warnings |
cargo fmt |
Rust | rustfmt.toml |
| ShellCheck | Bash | Default rules |
npm Publishing
npm publish --access public
# Package: @solana-clawd/pump-sdk
Vercel Website Deployment
# website/ directory — static HTML/CSS/JS
vercel --prod
MCP Server Distribution
npm publish --access public
# Package: @pump-fun/mcp-server
# Usage: npx -y @pump-fun/mcp-server
Patterns to Follow
- Use conventional commits for automated changelog generation
- Run
cargo clippyandcargo fmtbefore every Rust commit - Build TypeScript with both CJS and ESM output
- Test release builds before publishing
- Pin dependencies with lockfiles
Common Pitfalls
tsupmay not pick up all type exports — verify.d.tsoutputcargo build --releasetakes significantly longer than debug builds- npm
prepublishOnlyscripts should run tests and lint - Vercel deployment requires matching Node.js version
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 · 99 lines · 49 tokens per session scan A 47cc4c6a4320
pump-build-release is a skill published in the GitHub repository x402agent/solana-clawd (24 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 651 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.