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/contentstack/contentstack-iosWrote 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/contentstack/contentstack-ios/ios)<a href="https://agentmods.dev/rules/contentstack/contentstack-ios/ios"><img src="https://agentmods.dev/badge/rules/contentstack/contentstack-ios/ios/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/contentstack/contentstack-ios/ios"><img src="https://agentmods.dev/badge/rules/contentstack/contentstack-ios/ios.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.00000 | $0.00490 |
| Opus 5.5 | $0.00000 | $0.00196 |
| Sonnet 5.5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
ios 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS SDK Standards – Contentstack iOS CDA SDK
Apply these conventions when editing Objective-C code in the SDK (not test targets).
Language and runtime
- Objective-C with Apple’s modern conventions: use
NS_ASSUME_NONNULL_BEGIN/END(or explicitnullable/nonnull) on public headers where the project already does. - Swift consumers import the module; avoid breaking Swift names without good reason (Objective-C names map to Swift automatically).
Layout and modules
- Public API lives under
Contentstack/(headers shipped viapublic_header_filesin the podspec). - Internal implementation lives under
ContentstackInternal/(HTTP, URLs, constants, extensions). Do not expose internal headers as public API without an explicit decision. - Vendored / shared code under
ThirdPartyExtension/(e.g.CSURLSessionManager, markdown, ISO8601). Keep changes minimal and consistent with upstream vendoring policy.
Naming
- Classes: Prefix or unprefixed names as established in this SDK (
Stack,Config,CSIOCoreHTTPNetworking, etc.); do not introduce conflicting generic names. - Methods: Objective-C style, descriptive selectors; match existing patterns for “fetch”, “callback”, “withConfig:”, etc.
- Categories: Use project prefixes on category methods to avoid collisions (
cs_or existing project convention). - Test classes: See testing.mdc (
*TestXCTest case naming).
Headers
- Public declarations belong in
Contentstack/*.h; import umbrella patterns consistent withContentstack.h. - Use forward declarations (
@class) in headers when possible to reduce compile coupling.
Documentation
- Public API should retain or extend the existing block-comment style in headers (parameters, return value, Obj-C / Swift snippets where already used).
General
- Prefer explicit error handling over silent failure when adding new async or network paths.
- Match existing memory management (ARC); avoid introducing non-ARC patterns.
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 · 44 lines · 0 tokens per session scan A 3e7f5be0e63d
ios is a cursor rule published in the GitHub repository contentstack/contentstack-ios (3 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 490 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-09-04.
Other cursor rules, from other repositories
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
nativescript
NativeScript best practices and patterns for mobile applications.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
project-structure
Cursor rule "project-structure" from HeeGyeong/ComposeSample, covering project structure guide, layer structure, modularization rules, dependency rules and resource management.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.