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/r-huijts/xcode-mcp-server/path-managementgit clone --depth 1 https://github.com/r-huijts/xcode-mcp-serverWhat 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.01477 | $0.01477 |
| Opus 5 | $0.00739 | $0.00739 |
| Sonnet 5 | $0.00295 | $0.00295 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
path-management 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path Management System
This document provides a detailed explanation of the path management system used in the MCP Server. It covers the architecture, components, workflows, and security considerations.
Overview
The path management system provides a centralized, secure, and consistent way to handle file paths and directory navigation throughout the application. It was designed to address several key challenges:
- Security: Prevent access to unauthorized parts of the filesystem
- Consistency: Handle diverse path formats in a uniform manner
- Clarity: Provide clear error messages and path resolution
- Navigation: Support intuitive directory navigation with memory of previous locations
- Validation: Ensure paths meet security and format requirements
Components
The system consists of three main components:
1. PathManager
PathManager is the core class responsible for all path-related operations. It handles:
- Path normalization and expansion
- Security boundary enforcement
- Path validation for reading and writing
- Directory change tracking
- Path joining and relation checking
// Example: Creating and using PathManager
const pathManager = new PathManager(config);
pathManager.setProjectsBaseDir('/path/to/projects');
pathManager.setActiveProject('/path/to/projects/MyProject.xcodeproj');
// Normalize and validate paths
const normalizedPath = pathManager.normalizePath('~/projects/file.txt');
const isAllowed = pathManager.isPathAllowed(normalizedPath);
2. SafeFileOperations
SafeFileOperations builds on PathManager to provide secure file operations with consistent error handling. It includes:
- Safe file reading with validation
- Secure file writing with directory creation
- Safe directory listing
- Consistent error handling
// Example: Using SafeFileOperations
const fileOps = new SafeFileOperations(pathManager);
// Reading a file safely
const fileContent = await fileOps.readFile('config.json');
// Writing a file with proper validation
await fileOps.writeFile('settings.json', jsonContent, true);
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 · 205 lines · 1,477 tokens per session scan A 6580615b10ad
path-management is a cursor rule published in the GitHub repository r-huijts/xcode-mcp-server (385 stars, last pushed 7mo ago), licensed MIT. It adds 1,477 tokens to every session, about $0.0074 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-30.
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.