What is 09-cms-releases?

A guide to Contentstack Releases, which group related content changes so they can be published together. This is useful for campaigns, redesigns, or other updates that must go live as one set.

Use it to plan releases, add content items, stage deployments, schedule coordinated updates, and connect releases to a CI/CD pipeline—the automated process that builds and deploys software or content.

It reduces the risk of related content being published at different times or in the wrong order. It also helps avoid sending too many webhook notifications when many items change together.

09-cms-releases — Cursor rule by contentstack

Install

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.

agentmods

npx agentmods add rules/contentstack/contentstack-agent-skills/09-cms-releases

Clone the repo

git clone --depth 1 https://github.com/contentstack/contentstack-agent-skills

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 893 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00034	$0.00893
Opus 5	$0.00017	$0.00447
Sonnet 5	$0.00007	$0.00179
Haiku 4.5	$0.00003	$0.00089

Measured yesterday against content hash 63a6e628cb5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

09-cms-releases 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.

cursor/rules/09-cms-releases.mdc · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Releases

Description

Advise developers on using Contentstack Releases for coordinated, atomic content deployment. Cover release creation, item management, staged deployment, webhook storm prevention, and CI/CD integration.

When to Use

Use when developers ask about deploying multiple content changes together, campaign launches, coordinated content updates, release scheduling, or CI/CD content deployment.

User Problem

Developers need to deploy related content changes atomically so campaigns, redesigns, or coordinated updates go live together without manual coordination errors.

Success Criteria

Provides practical release workflow guidance. Explains webhook storm risks and mitigation. Shows CI/CD integration patterns when relevant. Correctly states release limitations and constraints.

Expected Inputs

Deployment coordination requirements
Number and type of content items
CI/CD pipeline details
Scheduling needs

Expected Outputs

Release workflow recommendations
Webhook storm prevention guidance
CI/CD integration patterns
Limitation awareness

Example User Requests

How do I deploy a campaign with 50 entries at once?
Can I schedule a release for a future date?
My static site rebuilds hundreds of times per release deployment.
How do I integrate releases with my CI/CD pipeline?
What are the limits on releases?

Workflow Summary

Understand the coordination requirements. Recommend release creation and item grouping. Advise staging validation before production. Warn about webhook storms and receiver debouncing. Cover CI/CD integration if applicable. State release limitations and when not to use releases.

Instructions

Release workflow

Create a release with a descriptive name. Add all related entries and assets, including items from multiple content types and locales. Deploy to staging first, validate, then deploy to production. Specify which version of each entry to deploy when needed.

Webhook storm

Read the full file on GitHub · 124 lines

Changes

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 · 124 lines · 34 tokens per session scan A 63a6e628cb5f

Subscribe to this mod's changes

09-cms-releases is a cursor rule published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 893 once invoked, about $0.0002 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.

DevOps and cloud Git and workflow Writing and docs

09-cms-releases