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/onflow/cadence-rulesWrote 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/onflow/cadence-rules/flow-configuration)<a href="https://agentmods.dev/rules/onflow/cadence-rules/flow-configuration"><img src="https://agentmods.dev/badge/rules/onflow/cadence-rules/flow-configuration/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/onflow/cadence-rules/flow-configuration"><img src="https://agentmods.dev/badge/rules/onflow/cadence-rules/flow-configuration.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.00055 | $0.04074 |
| Opus 5.5 | $0.00022 | $0.01630 |
| Sonnet 5.5 | $0.00011 | $0.00815 |
| Haiku 4.5 | $0.00006 | $0.00407 |
Grade A, and why
flow-configuration 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 652 lines · 55 tokens per session scan A cbc6b2647851
flow-configuration is a cursor rule published in the GitHub repository onflow/cadence-rules (3 stars, last pushed 5mo ago), with no licence file. It adds 55 tokens to every session and 4,074 once invoked, about $0.0002 per session on Opus 5.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-31.
Other cursor rules, from other repositories
helius-data-queries
Efficient data query patterns for Helius APIs.
dflow-trading
DFlow trading API rules for Solana swap and prediction market integrations.
helius-api-best-practices
Helius API best practices for Solana development.
phantom-wallet
Phantom Connect SDK integration rules for frontend Solana apps (React, React Native, browser).
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.