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/dx-delivery-sdknpx skills add contentstack/contentstack-agent-skills --skill 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.00000 | $0.02366 |
| Opus 5 | $0.00000 | $0.01183 |
| Sonnet 5 | $0.00000 | $0.00473 |
| Haiku 4.5 | $0.00000 | $0.00237 |
Grade A, and why
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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-delivery-sdk
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 ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 337 lines · 0 tokens per session scan A 5e9f6c6d77c1
dx-delivery-sdk 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 2,366 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.