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-variants-personalizationnpx skills add contentstack/contentstack-agent-skills --skill 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.00000 | $0.00839 |
| Opus 5 | $0.00000 | $0.00419 |
| Sonnet 5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
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 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cms-variants-personalization
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.
- 2d ago First seen · 119 lines · 0 tokens per session scan A f010bd982588
cms-variants-personalization is a skill published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 839 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…