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/contentstack/contentstack-ios/code-reviewgit 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/code-review)<a href="https://agentmods.dev/rules/contentstack/contentstack-ios/code-review"><img src="https://agentmods.dev/badge/rules/contentstack/contentstack-ios/code-review.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.00441 | $0.00441 |
| Opus 5 | $0.00220 | $0.00220 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
code-review 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.
What it actually says
Code Review Checklist – Contentstack iOS CDA SDK
Use this checklist when reviewing pull requests or before opening a PR.
API design and stability
- Public API: New or changed public classes/methods/properties are necessary and documented (header comments / doc comments where the project documents API).
- Backward compatibility: No breaking changes to public API unless explicitly called out and justified (e.g. major semver bump per release policy).
- Naming: Method and type names are consistent with existing SDK style (Objective-C / Swift import names) and CDA terminology.
Error handling and robustness
- Errors: API failures surface through existing patterns (
NSError **out-parameters, failure blocks, or delegate callbacks as used in the touched code). - Nullability:
NS_ASSUME_NONNULL/nullableannotations stay accurate; no unintended force-unwraps or ignored errors in new paths. - Memory / threading: Blocks and delegates retain cycles are avoided; main-queue vs background behavior matches existing networking code.
Dependencies and security
- Dependencies: No new third-party or vendored code without justification; version bumps are intentional and do not introduce known vulnerabilities.
- SCA: Address any security findings (e.g. from Snyk or similar) in the scope of the PR or in a follow-up.
Testing
- Coverage: New or modified behavior is covered by XCTest unit and/or integration-style tests as appropriate.
- Test quality: Tests are readable, stable (no flakiness), and follow project conventions (see testing.mdc).
Severity (optional)
- Blocker: Must fix before merge (e.g. breaking public API without approval, security issue, no tests for new code).
- Major: Should fix (e.g. inconsistent error handling, missing documentation on new public API).
- Minor: Nice to fix (e.g. style, minor docs).
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 · 37 lines · 441 tokens per session scan A 802a5f08ec54
code-review is a cursor rule published in the GitHub repository contentstack/contentstack-ios (3 stars, last pushed 29d ago), licensed MIT. It adds 441 tokens to every session, about $0.0022 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-09-04.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.