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.
git clone --depth 1 https://github.com/nirholas/pump-fun-sdkWrote 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/rules/nirholas/pump-fun-sdk/development-workflow)<a href="https://agentmods.dev/rules/nirholas/pump-fun-sdk/development-workflow"><img src="https://agentmods.dev/badge/rules/nirholas/pump-fun-sdk/development-workflow/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/rules/nirholas/pump-fun-sdk/development-workflow"><img src="https://agentmods.dev/badge/rules/nirholas/pump-fun-sdk/development-workflow.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.00000 | $0.00774 |
| Opus 5.5 | $0.00000 | $0.00310 |
| Sonnet 5.5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
development-workflow 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 117 lines · 0 tokens per session scan A 98882d8c4b54
development-workflow is a cursor rule published in the GitHub repository nirholas/pump-fun-sdk (136 stars, last pushed 6d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 774 tokens. 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 cursor rules, from other repositories
binance-net
Conventions for using Binance.Net library when working with Binance cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with Binance API.
kucoin-net
Conventions for using Kucoin.Net library when working with Kucoin cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with Kucoin API.
kraken-net
Conventions for using Kraken.Net when working with Kraken Spot and Futures cryptocurrency exchange APIs in C#/.NET. Apply when generating code that interacts with Kraken API.
hyperliquid-net
Conventions for using HyperLiquid.Net when working with the HyperLiquid DEX in C#/.NET, including spot, futures, account, HIP-3 DEX, and HIP-4 outcome APIs. Apply when generating code that interacts with the HyperLiquid API.
mexc-net
Conventions for using Mexc.Net library when working with the MEXC cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the MEXC API.
whitebit-net
Conventions for using WhiteBit.Net when working with the WhiteBit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with WhiteBit APIs.