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/onflow/cadence-rules/flow-development-workflowgit clone --depth 1 https://github.com/onflow/cadence-rulesWhat 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.00042 | $0.03322 |
| Opus 5 | $0.00021 | $0.01661 |
| Sonnet 5 | $0.00008 | $0.00664 |
| Haiku 4.5 | $0.00004 | $0.00332 |
Grade A, and why
flow-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 yesterday.
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.
- yesterday First seen · 496 lines · 42 tokens per session scan A 3ebf94f98fcc
flow-development-workflow is a cursor rule published in the GitHub repository onflow/cadence-rules (3 stars, last pushed 4mo ago), with no licence file. It adds 42 tokens to every session and 3,322 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-08-31.
Other cursor rules, from other repositories
core
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
no-auto-commit
Never commit or push without explicit user instruction.
00-global-architect
Global default behavior for the entire repository.