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 skills/contentstack/contentstack-agent-skills/cms-releasesnpx skills add contentstack/contentstack-agent-skills --skill cms-releasesgit 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.00000 | $0.00853 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cms-releases
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
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 · 121 lines · 0 tokens per session scan A 65e13f61243b
cms-releases is a skill published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 853 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-08-31.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
deploy-checklist
Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
deploy
Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".