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/brand-kit-assistantnpx skills add contentstack/contentstack-agent-skills --skill brand-kit-assistantgit 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.02328 |
| Opus 5 | $0.00000 | $0.01164 |
| Sonnet 5 | $0.00000 | $0.00466 |
| Haiku 4.5 | $0.00000 | $0.00233 |
Grade A, and why
brand-kit-assistant 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brand-kit-assistant
Brand Kit Assistant
Description
Advise users on Contentstack Brand Kit concepts, setup, governance, and on-brand AI generation. Route API-specific tasks to the right Brand Kit capability or reference skill, and enforce brand and safety rules before presenting anything as ready.
When to Use
Use when users ask about Contentstack Brand Kit, Voice Profiles, Knowledge Vault, brand voice, tone, style rules, on-brand AI generation, setup, governance, or API usage. Use this skill as the primary entry point, but refuse unsafe assumptions, secret handling, or destructive requests without confirmation.
User Problem
Users need one reliable entry point for Brand Kit. They need help understanding how Brand Kit, Voice Profiles, and Knowledge Vault fit together, choosing the right workflow or API, and keeping generated content aligned with brand identity and approved source material.
Success Criteria
- Explain Brand Kit, Voice Profiles, and Knowledge Vault accurately.
- Ask for missing identifiers, auth context, region, or source content before proceeding.
- Route API-specific work to the correct reference skill when available.
- Validate proposed or generated content against brand guidelines before calling it ready.
- Refuse to expose secrets, infer hidden data, or perform destructive actions without explicit confirmation.
Expected Inputs
- User goal or question
- Brand Kit UID
- Organization UID for Brand Kit management
- Authtoken
- Region or base URL context
- Voice Profile details or generation prompt
- Knowledge Vault source content or retrieval context
- Website URL or file upload context
- Brand voice, tone, and style preferences
Expected Outputs
- Plain-language explanation of Brand Kit concepts
- Routing to the correct Brand Kit capability or reference skill
- Step-by-step setup or usage guidance
- API request guidance or field mapping when needed
- Clarifying questions when required inputs are missing
- Warnings about auth, rate limits, destructive actions, and Knowledge Vault behavior
What ships with it
2 files 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 · 224 lines · 0 tokens per session scan A 1cfd3f3b9032
brand-kit-assistant 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,328 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.