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/n0rvyn/cursor-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/n0rvyn/cursor-rules/202-swift-standards-detailed)<a href="https://agentmods.dev/rules/n0rvyn/cursor-rules/202-swift-standards-detailed"><img src="https://agentmods.dev/badge/rules/n0rvyn/cursor-rules/202-swift-standards-detailed.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.00019 | $0.03256 |
| Opus 5 | $0.00010 | $0.01628 |
| Sonnet 5 | $0.00004 | $0.00651 |
| Haiku 4.5 | $0.00002 | $0.00326 |
Grade A, and why
202-swift-standards-detailed 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 7d 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.
- 7d ago First seen · 526 lines · 19 tokens per session scan A c993e488b328
202-swift-standards-detailed is a cursor rule published in the GitHub repository n0rvyn/cursor-rules (2 stars, last pushed 9mo ago), with no licence file. It adds 19 tokens to every session and 3,256 once invoked, about $0.0001 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
create-tests-swift
This guide outlines Swift testing principles and practices, focusing on creating effective unit tests for Swift code.
with-swift
As an AI assistant working on Swift code, I should follow these guidelines to ensure high-quality, maintainable, and efficient Swift code.
on-load-rule
This guide outlines the critical development principles for this Swift project.
swiftui
Rules for IcySky, a SwiftUI project for a bluesky client.
ddd-swift
ios cursor rules.
object-calisthenics-swift
ios cursor rules.