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/13-cms-variants-personalizationgit 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.00042 | $0.00884 |
| Opus 5 | $0.00021 | $0.00442 |
| Sonnet 5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
13-cms-variants-personalization 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Variants & Personalization
Description
Advise developers on using Contentstack Variants and Personalize for audience-targeted content. Explain when to use variants versus separate entries, how variant groups work, and how to integrate Personalize with the CMS.
When to Use
Use when developers ask about content personalization, A/B testing, audience segmentation, variant creation, or integrating Personalize with the CMS.
User Problem
Developers need to deliver different content to different audiences without duplicating entire entries or creating hard-to-maintain content structures.
Success Criteria
Clearly recommend variants vs separate entries. Provide practical integration guidance. Emphasize starting simple and adding complexity only when justified.
Expected Inputs
- Personalization requirements
- Audience segmentation needs
- Frontend framework
- Content variation scope
Expected Outputs
- Variants vs separate entries recommendation
- Integration pattern guidance
- SDK initialization instructions
- Complexity management advice
Example User Requests
- How do I show different content to different user segments?
- Should I use variants or create separate entries per audience?
- How do I integrate Personalize with my frontend?
- What are variant groups?
- Can I A/B test content in Contentstack?
Workflow Summary
Understand the personalization requirements. Recommend variants vs separate entries. Explain the Personalize integration pattern. Emphasize starting simple. Cover publishing and performance considerations.
Instructions
[]
Output Format
Be concise and advisory. Prefer direct recommendations over long explanations. Include a clear variants-vs-separate-entries decision. Mention simplicity and maintainability first.
Tooling Notes
Read-only advisory skill. Do not create, modify, or publish variants. Use Read, Grep, and Glob only.
Security
Defaults
Never expose tokens or API keys. Use environment variables for credentials in example code. Do not recommend hardcoding secrets in client-side code.
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 · 122 lines · 42 tokens per session scan A 1c1d785f924e
13-cms-variants-personalization is a cursor rule published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 15d ago), licensed MIT. It adds 42 tokens to every session and 884 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.
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.