Borrowing it
Nothing to install: this file belongs to parlay-run/parlay-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/parlay-run/parlay-mcp/main/GEMINI.mdgit clone --depth 1 https://github.com/parlay-run/parlay-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/parlay-run/parlay-mcp/gemini-md)<a href="https://agentmods.dev/instructions/parlay-run/parlay-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/parlay-run/parlay-mcp/gemini-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.00463 | $0.00463 |
| Opus 5 | $0.00231 | $0.00231 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
parlay-mcp GEMINI.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 6d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parlay — Prediction Market Tools
What this is
Parlay aggregates live prediction market data across real-money venues and sentiment markets through six MCP tools: search, brief, discovery, comparison, discrepancy scanning, and platform inspection.
When to use which tool
search_markets: use when the user wants keyword search across live prediction markets or event contracts.market_brief: use when the user wants an AI-ready summary of a topic, event, candidate, asset, or macro question.discover_markets: use when the user asks what is trending, high-volume, new, fast-moving, or ending soon.compare_markets: use when the user wants side-by-side comparison of the same event across venues.scan_discrepancies: use when the user asks for arbitrage, price gaps, spreads, or cross-venue disagreement.inspect_platform: use when the user names a specific venue and wants that venue's markets or coverage.
Venue coverage (Phase 1 validated)
- Polymarket + Kalshi = primary real-money
- Limitless = active real-money; systematic small premium on long-tail favorites (DIRECTIONAL SIGNAL, NOT executable arbitrage)
- Manifold = play-money only; hardcoded marketType:'sentiment'; excluded from real-money tools by design
- Opinion.trade = listed but ~no public liquidity (19/20 zero-volume in Phase 1 sample); NOT a broken connector
- Smarkets / Myriad / Metaculus / Probable / Baozi = catalog-only via PMXT
Critical caveats
- Manifold spreads vs Polymarket/Kalshi are NOT executable arbitrage (Manifold is play-money)
- Cross-platform event matches require human verification — same headline ≠ same market
- No canonical mapping exists between Kalshi tickers and Polymarket condition IDs
- Always cite the venue name and timestamp when stating probabilities
Behavioral guardrails
- Read-only tools: never claim to place trades, hold positions, or move funds
- Not financial advice: data is informational
- When the user asks for "arbitrage," surface cross-venue gaps but always note that execution risk, fees, and resolution criteria differences may eliminate the spread
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.
- 6d ago First seen · 36 lines · 463 tokens per session scan A 3de2e07057ae
parlay-mcp GEMINI.md is an instructions file published in the GitHub repository parlay-run/parlay-mcp (6 stars, last pushed 3mo ago), licensed MIT. It adds 463 tokens to every session, about $0.0023 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-31.
Other instructions, from other repositories
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.
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).
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).
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.
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.