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 rules/helius-labs/core-ai/helius-api-best-practicesgit clone --depth 1 https://github.com/helius-labs/core-aiWrote 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/helius-labs/core-ai/helius-api-best-practices)<a href="https://agentmods.dev/rules/helius-labs/core-ai/helius-api-best-practices"><img src="https://agentmods.dev/badge/rules/helius-labs/core-ai/helius-api-best-practices.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.1 | $0.00346 | $0.00346 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
helius-api-best-practices 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 6d 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.
What it actually says
API Keys
- Never hardcode Helius API keys in source files — always use environment variables
- Never expose API keys in client-side code (
NEXT_PUBLIC_env vars, browserfetch()URLs, WebSocket URLs) - Only Helius Sender (
https://sender.helius-rpc.com/fast) is browser-safe without an API key — proxy all other Helius API calls through a backend
Live Data
- Use Helius MCP tools for live blockchain data — never hardcode or mock chain state
- Never guess at credit costs or rate limits — check with
getRateLimitInfoorgetHeliusCreditsInfo - For errors, use the
troubleshootErrorMCP tool before attempting manual diagnosis
SDK Usage
- TypeScript:
import { createHelius } from "helius-sdk"thenconst helius = createHelius({ apiKey: process.env.HELIUS_API_KEY }) - Rust:
use helius::HeliusthenHelius::new("apiKey", Cluster::MainnetBeta)? - Handle rate limits with exponential backoff
Explorer Links
- ALWAYS use Orb (
https://orbmarkets.io) for transaction and account explorer links — never XRAY, Solscan, Solana FM, or any other explorer - Transaction:
https://orbmarkets.io/tx/{signature} - Account:
https://orbmarkets.io/address/{address} - Token:
https://orbmarkets.io/token/{token}
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.
- 6d ago First seen · 31 lines · 346 tokens per session scan A dbab80c907f7
helius-api-best-practices is a cursor rule published in the GitHub repository helius-labs/core-ai (26 stars, last pushed 2d ago), licensed MIT. It adds 346 tokens to every session, about $0.0017 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 cursor rules, from other repositories
cadence-nft-standards
Comprehensive standards and best practices for developing Non-Fungible Tokens (NFTs) using Cadence. Ensures proper implementation of NonFungibleToken interfaces, MetadataViews integration for marketplace compatibility, secure resource handling patterns, and advanced modular architectures for complex NFTs with traits…
flow-configuration
Comprehensive guide to Flow project configuration covering flow.json structure, CLI workflow, FCL integration, network management, and deployment best practices. Covers contract aliases, account management, dependency resolution, frontend FCL setup with React SDK, and environment-based configuration for seamless…
flow-development-workflow
Streamlined Flow development workflow covering documentation-first debugging methodology, iterative development approach, deployment verification, gas optimization strategies, and comprehensive testnet validation protocols. Focuses on practical workflows and error prevention rather than configuration details.
ai-generation-entrypoint
Start here — Happy Path (Restake): workflows/restaking-workflow.md.
user-preferences
Defines personalized development preferences and communication style for Flow blockchain development including concise response formatting, documentation-driven problem solving, iterative workflow methodology, full-stack awareness, and systematic error resolution. Guides AI behavior to match user's preferred…
verification-before-completion
Require fresh, scope-appropriate evidence before any completion claim. Distinguishes implemented, locally verified, repository-green, PR-green, deployed, and observed-stable states.