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/10-cms-roles-permissionsgit 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.00981 |
| Opus 5 | $0.00022 | $0.00491 |
| Sonnet 5 | $0.00009 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
10-cms-roles-permissions 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roles & Permissions
Description
Advise developers on designing roles, permissions, teams, and token access in Contentstack. Explain built-in roles, custom roles, permission merging, team-based access, and token capabilities with least-privilege guidance.
When to Use
Use when developers ask about user permissions, role design, team management, token capabilities, access control, or automation access in Contentstack.
User Problem
Developers need to grant the right level of access to users, teams, and automation without over-privileging or creating security gaps.
Success Criteria
Recommends the principle of least privilege. Explains built-in roles, custom role design, permission merging, teams, and token capabilities clearly. Distinguishes safe client-side tokens from server-side credentials. Flags rate-limit and SSO edge cases when relevant.
Expected Inputs
- Team structure and user types
- Access control requirements
- Automation or integration needs
- SSO or compliance requirements
Expected Outputs
- Role design recommendations
- Custom role configuration guidance
- Team setup guidance
- Token selection recommendations
- Permission merging explanations
Example User Requests
- What built-in roles does Contentstack have?
- How do I restrict editors to only certain content types?
- What can management tokens do vs authtokens?
- How do I set up teams for multiple stacks?
- What happens when a user has multiple roles?
Workflow Summary
Understand the team structure and access needs. Recommend built-in roles or custom roles as appropriate. Explain permission merging if multiple roles apply. Guide on teams for larger organizations. Recommend the right token type for automation.
Instructions
Built-in roles
Explain the default roles first: Owner, Admin, Developer, and Content Manager. Use them when they meet the need; otherwise recommend a custom role.
Custom roles
Use custom roles when access must be limited by content type, environment, locale, branch, or action. Describe permissions by module, content type, and action. Use $all for all instances when applicable.
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 · 130 lines · 43 tokens per session scan A 9d60ee0db001
10-cms-roles-permissions 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 981 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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.