Borrowing it
Nothing to install: this file belongs to pgomsan/upv-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/pgomsan/upv-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/pgomsan/upv-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/pgomsan/upv-mcp/claude-md)<a href="https://agentmods.dev/instructions/pgomsan/upv-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pgomsan/upv-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.00791 | $0.00791 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
upv-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 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
upv-mcp
Servidor MCP local con el calendario academico de la UPV y PoliformaT. SDK mcp
2.x (la clase es MCPServer; en la 1.x era FastMCP). Transporte stdio.
Comandos
uv sync # instalar
uv run pytest -q # tests
uv run mypy # strict, debe salir limpio
uv run ruff check . # lint (ruff format . para formatear)
uv run upv-mcp # arrancar el servidor (stdio)
uv run upv-mcp-config show # ver que credenciales estan configuradas
Los cuatro primeros deben pasar antes de dar por terminado un cambio.
Invariantes de arquitectura
Romperlos es el unico motivo real para rechazar un PR aqui.
sources/no importamcp. Solo red + parseo -> modelos de dominio.tools/no importamcp, nihttpx2, niicalendar. Solo modelos +repository.server.pyes el UNICO fichero que importamcp.tests/test_architecture.pylo comprueba conast: rompe la build si se viola.
Datos
- El
.icsreal no se commitea. Los fixtures detests/fixtures/son anonimizados y conservan la estructura exacta del generador de la UPV. - Credenciales (URL iCal con token, usuario y clave UPV) van al llavero via
upv-mcp-config. Nunca a un fichero ni a un.env. - Todo datetime se normaliza a Europe/Madrid al parsear, nunca en
tools/. - Peculiaridades de cada origen: docstrings de
sources/ics.py,poliformat.pyycas.py. Leelos antes de tocarlos; no estan documentadas en ningun sitio publico. - PoliformaT NO permite login por API: solo CAS. Un login rechazado no se reintenta nunca, porque bloquea la cuenta.
- Los examenes vienen de su propio iCal (opcional). Nunca los deduzcas del titulo de una tarea: hay tareas llamadas "Examen" que no lo son, y al reves.
Convenciones de tools
- Nombre en
snake_case, verbo primero:get_schedule,list_upcoming_deadlines. - Una tool por modulo en
tools/, registrada enserver.py. - Navegar contenido va como resource; descargarlo y convertirlo, como tool.
- La descripcion es codigo de produccion, no documentacion: decide si el modelo elige bien. Di que devuelve, cuando usarla y cuando NO, redirigiendo por nombre a la tool correcta.
- Devolver datos estructurados y compactos: filtrar, ordenar y truncar antes de
responder. Al truncar,
meta.truncated = true. - Si una tool no puede ver algo, decirlo en
meta.coverage_note. Es lo que impide que el modelo afirme "no tienes examenes" cuando no los esta mirando.
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 · 65 lines · 791 tokens per session scan A 505403f17237
upv-mcp CLAUDE.md is an instructions file published in the GitHub repository pgomsan/upv-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 791 tokens to every session, about $0.0040 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.