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/11-cms-taxonomygit 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.00043 | $0.00982 |
| Opus 5 | $0.00022 | $0.00491 |
| Sonnet 5 | $0.00009 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
11-cms-taxonomy 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contentstack Taxonomy
Description
Advise developers on using Contentstack Taxonomy for structured, hierarchical content classification and delivery-side filtering. Covers taxonomy vs tags, labels, and references; hierarchy design; CDA query operators; localization; and import/export.
When to Use
Use when developers need help classifying content, designing category hierarchies, choosing between taxonomy and other classification approaches, or querying entries by category on the delivery side.
User Problem
Developers need a governed way to classify content so it can be filtered, navigated, and organized in delivery experiences. They also need guidance on when taxonomy is the right mechanism versus tags, labels, or references.
Success Criteria
Recommends taxonomy only when it fits the use case Explains hierarchy design and term relationships clearly Uses CDA taxonomy operators for filtering examples Distinguishes taxonomy from tags, labels, and references Covers localization and import/export when relevant
Expected Inputs
- Classification or filtering requirements
- Hierarchy depth and structure
- Delivery-side query needs
- Localization requirements
- Migration or import needs
Expected Outputs
- Taxonomy vs alternatives recommendation
- Hierarchy design guidance
- CDA query operator examples
- Localization guidance
- Import/export advice
Example User Requests
- Should I use taxonomy or tags for product categories?
- How do I query entries by taxonomy term on the CDA?
- How do I design a taxonomy hierarchy for my site?
- Can I localize taxonomy terms?
- Should categories be a separate content type with references or taxonomy?
Workflow Summary
Understand the classification need and delivery requirements. Recommend the right mechanism: taxonomy, tags, labels, or references. If taxonomy fits, guide hierarchy design and term modeling. Show CDA taxonomy query operators for filtering. Cover localization and import/export if relevant.
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 · 127 lines · 43 tokens per session scan A a7b2f12bdb53
11-cms-taxonomy is a cursor rule published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 15d ago), licensed MIT. It adds 43 tokens to every session and 982 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
internationalization
Cursor rule "internationalization" from dtyq/magic, covering internationalization (i18n) rules, 国际化基本规范, 1. 文件结构, 2. 命名空间规范 and 3. 组件中使用国际化.
07-datagen
IF 生成物品/方块模型 JSON → 手动编写 JSON 在 src/main/resources/assets/{modid}/models/.
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
wings
Authoring apps with the WINGS framework (Go compiled to WASM web components).
project-status
PriceGrab shipped state and product backlog (read first).
architecture
Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.