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.
git clone --depth 1 https://github.com/0xChron/polymarket-mcpWrote 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/0xchron/polymarket-mcp/python-conventions)<a href="https://agentmods.dev/rules/0xchron/polymarket-mcp/python-conventions"><img src="https://agentmods.dev/badge/rules/0xchron/polymarket-mcp/python-conventions/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/0xchron/polymarket-mcp/python-conventions"><img src="https://agentmods.dev/badge/rules/0xchron/polymarket-mcp/python-conventions.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.00000 | $0.00273 |
| Opus 5.5 | $0.00000 | $0.00109 |
| Sonnet 5.5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
python-conventions 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.
What it actually says
Python Conventions
Required
- Type hints on all functions and tool parameters (
str | None,list[dict],Literalfor enums) - All I/O is
async; useasyncio.gatherfor parallel API calls - Use
uvfor dependencies — neverpipdirectly
Imports
Match package import style:
from polymarket_mcp.config import Settings
from polymarket_mcp.utils.helpers import err, get, text
from polymarket_mcp.utils.formatters import format_search_markets
Naming
- Functions/tools:
snake_case(get_user_positions) - Types:
PascalCase(Settings,Category) - MCP tool name matches function name
HTTP Params
Filter None values before API calls — do not send null query params:
params = {"q": query, "events_status": "active" if active_only else None}
data = await get(url, params=params) # helpers filters None
Scope
- Keep changes minimal and focused
- Match surrounding code style; no over-abstraction
- Add comments only for non-obvious business logic
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 · 45 lines · 0 tokens per session scan A 5e0521c1031a
python-conventions is a cursor rule published in the GitHub repository 0xChron/polymarket-mcp (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 273 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.
Other cursor rules, from other repositories
python-best-practices
Guidelines for professional Python development, including Pydantic v2, Python 3.13 typing, Ruff and testing.
10-python
Python conventions for agent-gate.
client-library
A design guide for a Python client that connects to Japan’s Real Estate Information Library API, a service providing real-estate data. It covers API-key setup, request settings, and typed data models.
api-development
Python rules for building clients for Japan’s real-estate information API, a service that provides property and geographic data.
project-structure
A project-structure guide for an MCP server and Python library using Japan’s Ministry of Land, Infrastructure, Transport and Tourism real-estate information API.
python-code-validator
Validate generated Python at every step, not once at the end.