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/contentstack-ios-cda)<a href="https://agentmods.dev/rules/contentstack/contentstack-ios/contentstack-ios-cda"><img src="https://agentmods.dev/badge/rules/contentstack/contentstack-ios/contentstack-ios-cda/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/contentstack-ios-cda"><img src="https://agentmods.dev/badge/rules/contentstack/contentstack-ios/contentstack-ios-cda.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.00567 |
| Opus 5.5 | $0.00000 | $0.00227 |
| Sonnet 5.5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
contentstack-ios-cda 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contentstack iOS CDA – SDK Rules
Apply when editing the SDK core (Contentstack/, ContentstackInternal/). Keep behavior aligned with the Content Delivery API.
Stack and Config
- Entry point:
+[Contentstack stackWithAPIKey:accessToken:environmentName:]andstackWithAPIKey:accessToken:environmentName:config:return aStack. UseConfigfor optional settings (host, region, branch, delegate, early access). - Defaults: Follow existing
Configinitialization (host/version behavior as implemented inConfig/ stack setup). - Region / branch: Support regional endpoints and branch delivery via
Configproperties, consistent with CDA docs and current stack URL building (CSIOAPIURLs, etc.).
HTTP layer
- Requests should flow through
CSIOCoreHTTPNetworkingandCSURLSessionManager(and related internal types). Do not bypass the shared session stack for CDA calls without a strong reason. - Headers: Preserve User-Agent, access token, environment, and other required CDA headers as built in existing request code (
CSIOConstants, stack configuration). - Errors: Map API failures to existing patterns (
NSError, failure blocks, or error callbacks) so app code receives consistent semantics.
Retry and resilience
- Retry logic for transient failures lives in the networking layer (e.g.
CSIOCoreHTTPNetworkinghandling of status / error codes). When changing retry behavior, keep defaults and caps consistent with CDA-friendly backoff and document any behavior change. - Unlike some other SDKs, retry is not always exposed as a separate public
Configsurface; prefer adjusting the internal implementation coherently.
Callbacks and async
- Use blocks, delegates (
CSURLSessionDelegate), and existing completion patterns already used onStack,Entry,Query,Asset,SyncStack, etc. - Do not change public callback signatures without a compatibility plan (semver / migration note).
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 · 37 lines · 0 tokens per session scan A 3df1ddec250f
contentstack-ios-cda 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 567 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
api
Get system information: getApp(), getSystemInfoSync() Lifecycle management: application-level events such as onLaunch and onShow.
api-ui-binding
Cursor rule "api-ui-binding" from HeeGyeong/ComposeSample, covering api and ui binding creation rules, requirements, 1. dto creation, 2. api interface and 3. api call function implementation.
api-creation-guide
Cursor rule "api-creation-guide" from HeeGyeong/ComposeSample, covering api creation guide rules, requirements, api call function, constraints and expected results.
mobile-api-generation-flow
Explain backend-to-mobile API generation flow.
dependency-injection
Hilt dependency injection rules: modules, scoping, testing, Compose integration.
android-networking-retrofit-okhttp
Build Android networking stacks with Retrofit, OkHttp, interceptors, API contracts, and resilient error handling.