Borrowing it
Nothing to install: this file belongs to MoayadAbbara/FPL-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/MoayadAbbara/FPL-MCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/MoayadAbbara/FPL-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/moayadabbara/fpl-mcp/claude-md)<a href="https://agentmods.dev/instructions/moayadabbara/fpl-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/moayadabbara/fpl-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.00768 | $0.00768 |
| Opus 5 | $0.00384 | $0.00384 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
FPL-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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FPL MCP
An MCP server for Fantasy Premier League. Local-first (stdio): reads the user's team, analyses players, and will manage transfers/captain/chips. Unofficial, uses the public FPL API.
Commands (this project uses uv)
- Install/sync:
uv sync --extra dev - Run server:
uv run python src/server.py - Format + lint:
uv run ruff format . && uv run ruff check --fix . - Tests:
uv run pytest -q - Quick tool check:
uv run python -c "import sys; sys.path.insert(0,'src'); import asyncio; from server import mcp; print([t.name for t in asyncio.run(mcp.list_tools())])"
Layout
This is an application, not a library ([tool.uv] package = false). Code lives flat under
src/ — no src/fpl_mcp/ package wrapper. Running python src/server.py puts src/ on the
import path, so modules import as top-level: from api.client import ..., from domain.team import ....
Architecture — layered, each layer only knows the one below
src/
tools/ MCP tool surface (thin glue: fetch -> domain -> format -> str)
format/ raw data -> compact, model-friendly TEXT
domain/ pure FPL logic (dataclasses; knows NO http/mcp) -> easy to test
api/ FPL HTTP client (httpx). No caching yet — kept simple on purpose.
auth/ token storage & expiry (token.txt for now)
config.py central constants (URLs, client_id, TTLs)
server.py entry point only: build app, register tools, run stdio
Non-negotiable rules
- Never return raw FPL JSON to the model. bootstrap-static is ~500k tokens; always
go through
domain/thenformat/and return only decision-relevant fields. domain/stays pure — no httpx, no mcp imports. It takes dicts, returns dataclasses.- Tool names:
snake_case, multi-word, ≤8 params. Lightweight output by default; add adetailed=Trueflag for the verbose view rather than always dumping everything. - Read tools in
tools/read_tools.py, write tools (transfer/captain/chip) go intools/write_tools.pywhen we build them — keep the two separate.
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.
- 7d ago First seen · 57 lines · 768 tokens per session scan A fd8e8f853749
FPL-MCP CLAUDE.md is an instructions file published in the GitHub repository MoayadAbbara/FPL-MCP (0 stars, last pushed 16d ago), licensed MIT. It adds 768 tokens to every session, about $0.0038 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
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.