dev-workflow

Development instructions for a Python MCP project that uses uv, Docker, and automated tests. They describe how to manage dependencies, run the server, build its container, and test it.

In plain words
What is it for?
Use them to install dependencies with uv, run or containerize the Polymarket MCP server, launch the MCP Inspector, and run its pytest tests.
Why use it?
They provide the project’s expected commands and dependency rules, reducing setup mistakes and preventing accidental changes to the lockfile.

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/0xchron/polymarket-mcp/dev-workflow
Clone the repo
git clone --depth 1 https://github.com/0xChron/polymarket-mcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 290 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00000 $0.00290
Opus 5 $0.00000 $0.00145
Sonnet 5 $0.00000 $0.00058
Haiku 4.5 $0.00000 $0.00029

Measured yesterday against content hash 413679baa3d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev-workflow 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 yesterday.

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.

.cursor/rules/dev-workflow.mdc · 39 lines

What it actually says

Dev Workflow

Package Management

  • Only uv — never pip install directly
  • Add deps: uv add <package>
  • Run tools: uv run --frozen <command> (always pass --frozen to avoid rewriting uv.lock)
  • Sync env: uv sync

Common Commands

make run        # uv run --frozen polymarket-mcp
make test       # uv run --frozen pytest
make inspector  # npx @modelcontextprotocol/inspector
make build      # docker build -t polymarket-mcp .
make start      # docker run -p 8000:8000

Docker

  • Package installed via uv sync --frozen in the image
  • Server entrypoint: uv run --frozen polymarket-mcp
  • Server listens on port 8000 (streamable-http)

Testing

Run make test. Uses pytest with respx for HTTP mocking.

Dependencies

Declare direct dependencies in pyproject.toml if imported in source (e.g. httpx, pydantic-settings), not only as transitive deps of mcp.

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. yesterday First seen · 39 lines · 0 tokens per session scan A 413679baa3d9

Subscribe to this mod's changes

dev-workflow is a cursor rule published in the GitHub repository 0xChron/polymarket-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 290 tokens. 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.