Borrowing it
Nothing to install: this file belongs to Skeyelab/directus-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Skeyelab/directus-mcp-server/main/.cursorrulesgit clone --depth 1 https://github.com/Skeyelab/directus-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/skeyelab/directus-mcp-server/cursorrules)<a href="https://agentmods.dev/rules/skeyelab/directus-mcp-server/cursorrules"><img src="https://agentmods.dev/badge/rules/skeyelab/directus-mcp-server/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/skeyelab/directus-mcp-server/cursorrules"><img src="https://agentmods.dev/badge/rules/skeyelab/directus-mcp-server/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00506 | $0.00506 |
| Opus 5.5 | $0.00202 | $0.00202 |
| Sonnet 5.5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
cursorrules 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directus MCP Server Cursor Rules
Toolset Organization
When adding new tools or features to this MCP server, always organize them into appropriate toolsets:
-
Schema and Content tools must belong to the
defaulttoolset - This ensures backward compatibility and allows clients to access core tools when no specific toolset is requested. -
Flow tools do NOT belong to the
defaulttoolset - Flow tools are only in theflowtoolset and must be explicitly requested. -
Assign tools to their specific toolset:
- Schema-related tools →
schematoolset (collections, fields, relations, schema snapshots) - Content-related tools →
contenttoolset (items CRUD, queries, bulk operations) - Flow-related tools →
flowtoolset (workflow automation, triggers) - NOT in default
- Schema-related tools →
-
Toolset assignment format:
// For schema and content tools: { name: 'tool_name', description: 'Tool description', inputSchema: z.object({...}), toolsets: ['default', 'schema'] as const, // Always include 'default' + specific toolset handler: async (client, args) => {...} } // For flow tools: { name: 'tool_name', description: 'Tool description', inputSchema: z.object({...}), toolsets: ['flow'] as const, // Only 'flow', NOT 'default' handler: async (client, args) => {...} } -
When creating new tool files:
- Determine which toolset the tools belong to based on their functionality
- Schema and content tools: Add to both
defaultand their specific toolset - Flow tools: Add ONLY to
flowtoolset (notdefault) - Update the toolset filtering logic in
src/index.tsif adding a new toolset category
-
Toolset types are defined in
src/types/index.tsas:export type Toolset = 'default' | 'schema' | 'content' | 'flow';
This organization allows clients to filter tools using the MCP_TOOLSETS environment variable, improving AI agent accuracy by reducing tool confusion. The default toolset contains only schema and content tools, while flow tools must be explicitly requested.
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.
- 1mo ago First seen · 49 lines · 506 tokens per session scan A 67166ab16c97
cursorrules is a cursor rule published in the GitHub repository Skeyelab/directus-mcp-server (0 stars, last pushed 11mo ago), licensed MIT. It adds 506 tokens to every session, about $0.0020 per session on Opus 5.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-09-01.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
server-state
USE WHEN: Fetching and caching server data with TanStack Query 5: queryOptions, hooks, mutations, invalidation.
selectools-providers
Rules for working with LLM provider adapters in selectools.