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-agent-skills/17-dx-delivery-sdkgit clone --depth 1 https://github.com/contentstack/contentstack-agent-skillsWhat 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.00062 | $0.02433 |
| Opus 5 | $0.00031 | $0.01216 |
| Sonnet 5 | $0.00012 | $0.00487 |
| Haiku 4.5 | $0.00006 | $0.00243 |
Grade A, and why
17-dx-delivery-sdk 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 2d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-delivery-sdk
Description
Help agents write correct, production-ready TypeScript using @contentstack/delivery-sdk for Contentstack entries, assets, references, filtering, sorting, pagination, locale, Live Preview, and Visual Builder support. Verify SDK behavior against the Delivery SDK Spec when method names, options, or chain order matter.
When to Use
Use when a user asks for Contentstack Delivery SDK code, query examples, helper functions, SDK setup, stack initialization, reference inclusion, filtering, sorting, pagination, typed entry fetching, asset fetching, Live Preview setup, Visual Builder support, SSR preview handling, or debugging SDK query chains.
User Problem
Users need current, correct Contentstack Delivery SDK code with the right method names, chain order, and query patterns. The skill should prevent subtle SDK mistakes and default to production-ready TypeScript.
Success Criteria
- Uses current
@contentstack/delivery-sdkmethod names and correct chain order. - Verifies API details against the Delivery SDK Spec when behavior is uncertain.
- Produces TypeScript-first examples with safe environment-based credentials.
- Handles references, filters, sorting, pagination, field selection, assets, locale, and Live Preview correctly.
- Flags or avoids common mistakes such as wrong query methods, missing pagination, or shared SSR Live Preview stacks.
Expected Inputs
- Content type UID
- Entry UID or asset UID when applicable
- Field UIDs for filters, sorting, selection, or references
- Locale when localized content is needed
- Desired return shape or helper function behavior
- SSR or Visual Builder context when Live Preview is involved
Expected Outputs
- TypeScript code snippets
- Reusable helper functions
- Correct SDK query chains
- Live Preview or SSR-safe stack setup
- Debugging guidance for incorrect Contentstack SDK usage
Example User Requests
- Write a Contentstack Delivery SDK query for blog posts with author references included.
- Show me the correct TypeScript setup for Contentstack Live Preview in Next.js SSR.
- Fix this Contentstack query chain; it is not returning the right entries.
- Create a helper to fetch entries by URL with pagination and typing.
- How do I fetch assets and filter by content type in
@contentstack/delivery-sdk?
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.
- 2d ago First seen · 340 lines · 62 tokens per session scan A 6378ed92bd17
17-dx-delivery-sdk is a cursor rule published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 15d ago), licensed MIT. It adds 62 tokens to every session and 2,433 once invoked, about $0.0003 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.