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 instructions/skeyelab/directus-mcp-server/copilot-instructionsgit 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/instructions/skeyelab/directus-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/skeyelab/directus-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/skeyelab/directus-mcp-server/copilot-instructions.svg" alt="Measured on agentmods" 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 | $0.02433 | $0.02433 |
| Opus 5 | $0.01216 | $0.01216 |
| Sonnet 5 | $0.00487 | $0.00487 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade A, and why
directus-mcp-server copilot-instructions.md 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 4d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
Project Overview
This is a Model Context Protocol (MCP) server that provides comprehensive tools for managing Directus schema and content. It enables AI assistants and other MCP clients to interact with Directus instances programmatically.
Key Technologies:
- TypeScript (ES2022, Node16 modules)
- Model Context Protocol SDK (
@modelcontextprotocol/sdk) - Directus SDK (
@directus/sdk) - Zod for runtime validation
- Vitest for testing
- ESLint for linting
Project Structure
src/
├── index.ts # Main MCP server entry point
├── directus-client.ts # Directus API client with auth & resource factories
├── directus-client.test.ts # Client tests
├── tools/ # MCP tool implementations & utilities
│ ├── tool-helpers.ts # Helper functions for creating tools
│ ├── validators.ts # Shared Zod schemas and validators
│ ├── schema-tools.ts # Collection, field, relation management
│ ├── schema-tools.test.ts
│ ├── content-tools.ts # CRUD operations for items
│ ├── content-tools.test.ts
│ ├── flow-tools.ts # Directus flow management
│ └── flow-tools.test.ts
└── types/ # TypeScript type definitions
└── index.ts
Development Workflow
Building
npm run build # Compile TypeScript to dist/
npm run dev # Watch mode for development
Testing
npm test # Run all tests with Vitest
npm run test:watch # Watch mode
npm run test:coverage # With coverage report
Linting
npm run lint # Check for issues
npm run lint:fix # Auto-fix issues
Code Style and Conventions
TypeScript
- Use ES2022 features with Node16 module resolution
- Strict mode is enabled - leverage full type safety
- Use explicit return types for exported functions
- Avoid
anytypes (allowed in tests only) - Use
interfacefor public API types,typefor unions/intersections
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.
- 4d ago First seen · 345 lines · 2,433 tokens per session scan A 48dbe1813248
directus-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository Skeyelab/directus-mcp-server (0 stars, last pushed 9mo ago), licensed MIT. It adds 2,433 tokens to every session, about $0.0122 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-09-01.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).