project-development

Development rules for exarp, a Python MCP server that exposes project-management automation tools. They define code style, formatting, linting, type checking, testing, and the required uv-based setup.

In plain words
What is it for?
Use them when developing the server, managing its Python environment, formatting code, checking types, linting, or running tests.
Why use it?
They keep development work consistent and document how to install dependencies and verify changes.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/davidl71/project-management-automation/project-development
Clone the repo
git clone --depth 1 https://github.com/davidl71/project-management-automation

Made for: Cursor.

Per session 2,149 This file is loaded in full into every session.
When invoked 2,149 The same file — it is already loaded in full.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02149 $0.02149
Opus 5 $0.01074 $0.01074
Sonnet 5 $0.00430 $0.00430
Haiku 4.5 $0.00215 $0.00215

Measured 2d ago against content hash 4b09520f7499, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

project-development scanned grade C with 2 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -LsSf https://astral.sh/uv/install.sh | sh

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -LsSf https://astral.sh/uv/install.sh | sh
.cursor/rules/project-development.mdc · 335 lines

How it starts

The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Management Automation - Development Rules

This document provides development guidelines and conventions for the Project Management Automation MCP Server.

Project Overview

Type: Python MCP Server Purpose: Expose project management automation tools via Model Context Protocol Package Name: exarp (Extended Automation & Research Platform) MCP Server Identifier: exarp

Code Style

  • Python Version: >= 3.9
  • Code Formatter: Black (default configuration)
  • Linter: Ruff
  • Type Checking: mypy (strict mode recommended)
  • Testing: pytest with pytest-mock

Development Workflow

1. Setup Development Environment

🚨 CRITICAL: This project uses uv for package management. NEVER use pip directly.

# Install dependencies and sync environment (REQUIRED - uses uv.lock)
uv sync

# This replaces the old: pip install -e '.[dev]'
# uv automatically handles editable installs and dev dependencies

Why uv?

  • 10-100x faster than pip
  • Automatic environment management
  • Better dependency resolution
  • Project has uv.lock file configured

If uv is not available:

# Install uv first
curl -LsSf https://astral.sh/uv/install.sh | sh
# Or: pipx install uv

2. Running Tests

Always use uv run to execute commands in the managed environment:

# Run all tests
uv run pytest tests/ -v

# Run specific test file
uv run pytest tests/test_tools.py -v

# Run with coverage
uv run pytest tests/ --cov=project_management_automation --cov-report=html

3. Code Quality Checks

Always use uv run to execute commands in the managed environment:

# Format code
uv run black .

# Type check
uv run mypy .

# Lint
uv run ruff check .

4. Testing MCP Server

Always use uv run to execute commands in the managed environment:

# Run server directly for testing
uv run python -m project_management_automation.server

# Or use the exarp command
uv run exarp --version

Read the full file on GitHub · 335 lines

Changes

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.

  1. 2d ago First seen · 335 lines · 2,149 tokens per session scan C 4b09520f7499

Subscribe to this mod's changes

project-development is a cursor rule published in the GitHub repository davidl71/project-management-automation (1 stars, last pushed 6mo ago), licensed MIT. It adds 2,149 tokens to every session, about $0.0107 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.