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/dflow-tradinggit 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/dflow-trading)<a href="https://agentmods.dev/rules/helius-labs/core-ai/dflow-trading"><img src="https://agentmods.dev/badge/rules/helius-labs/core-ai/dflow-trading.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.00000 | $0.00337 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
dflow-trading 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 4d 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
CORS & Backend Proxy
- ALWAYS proxy DFlow Trade API calls through a backend for web apps — DFlow does not set CORS headers, so direct browser calls will silently fail
- Dev endpoints are for testing only — do not ship to production without a DFlow API key from
pond.dflow.net/build/api-key
Amounts
- ALWAYS use atomic units for
amount—1_000_000_000for 1 SOL,1_000_000for 1 USDC; passing decimal values will produce incorrect trades
Async Order Handling
- ALWAYS poll
/order-statusfor async trades — prediction markets and imperative trades withexecutionMode: "async"do not return a transaction synchronously - ALWAYS check market
status === 'active'before submitting prediction market orders - Handle the Thursday 3–5 AM ET maintenance window for prediction markets
KYC
- ALWAYS check Proof KYC status before prediction market trades — gate at trade time, not at browsing time
Transaction Submission
- ALWAYS submit DFlow transactions via Helius Sender — never raw
sendTransactionto standard RPC - DFlow
/orderwithpriorityLevelhandles priority fees and Jito tips automatically — do not add duplicate compute budget instructions - For custom (non-DFlow) transactions, follow the standard Sender rules:
setComputeUnitPrice+setComputeUnitLimit+ Jito tip
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.
- 4d ago First seen · 31 lines · 0 tokens per session scan A ed9ac4973f09
dflow-trading is a cursor rule published in the GitHub repository helius-labs/core-ai (26 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 337 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
x402-protocol
x402 v2 protocol conventions and the OpenDexter hosted-authority boundary.
530-glob-patterns
description: WHEN defining glob patterns in Cursor Rule (.mdc) files ENSURE using precise and optimized patterns globs: ["/.mdc"] alwaysApply: false.
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.
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…