Borrowing it
Nothing to install: this file belongs to fieldviolence/polyrouter-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fieldviolence/polyrouter-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/fieldviolence/polyrouter-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/instructions/fieldviolence/polyrouter-mcp/claude-md)<a href="https://agentmods.dev/instructions/fieldviolence/polyrouter-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/fieldviolence/polyrouter-mcp/claude-md.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.1 | $0.01019 | $0.01019 |
| Opus 5 | $0.00509 | $0.00509 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
polyrouter-mcp CLAUDE.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 8d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
bun install # Install dependencies
bun run build # Build to dist/
bun run dev # Run in development mode (no build)
bun run start # Run built version
bun run type-check # TypeScript type checking
Architecture
This is a Model Context Protocol (MCP) server that provides:
- Unified read access to prediction market platforms via the Polyrouter API (Polymarket, Kalshi, Limitless, Manifold)
- Direct trading capabilities on Kalshi and Polymarket via their official SDKs
File Structure
src/
├── index.ts # Main MCP server + all tool definitions
├── trading/
│ ├── types.ts # Shared trading interfaces
│ ├── kalshi.ts # Kalshi SDK wrapper
│ ├── polymarket.ts # Polymarket CLOB client wrapper
│ └── unified.ts # Unified router + order preview state
Tool Pattern
Each tool follows this pattern:
server.tool(
"tool_name",
"Description",
{ /* Zod schema for params */ },
async (params) => {
const data = await makeRequest("/endpoint", params);
return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
}
);
Environment Variables
Create a .env file with:
# Required - Polyrouter API (for market data)
POLYROUTER_API_KEY=xxx
POLYROUTER_BASE_URL=https://api-v2.polyrouter.io # Optional, defaults to production
# Optional - Kalshi Trading
KALSHI_API_KEY=xxx
KALSHI_API_SECRET=xxx # RSA private key - see note below
# Optional - Polymarket Trading
POLYMARKET_PRIVATE_KEY=xxx # Ethereum private key (with 0x prefix)
POLYMARKET_FUNDER_ADDRESS=xxx # Your Polymarket profile address (optional)
Kalshi RSA Key Format
The Kalshi API secret is an RSA private key. In .env files, you must put the entire key on a single line with literal \n characters:
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.
- 8d ago First seen · 126 lines · 1,019 tokens per session scan A 4443cd8578e8
polyrouter-mcp CLAUDE.md is an instructions file published in the GitHub repository fieldviolence/polyrouter-mcp (31 stars, last pushed 7mo ago), licensed MIT. It adds 1,019 tokens to every session, about $0.0051 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 instructions, from other repositories
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).
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.
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).
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.