What is pvpc-mcp-server AGENTS.md?

A project instruction file for AI coding agents working on an MCP server, a service that lets AI tools access external capabilities.

Use it to guide file edits, dependency changes, version updates, commits, tests, linters, and type checks in the rfdez/pvpc-mcp-server project.

It gives agents consistent rules for safe, focused changes and explains which checks to run.

How rfdez/pvpc-mcp-server configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to rfdez/pvpc-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rfdez/pvpc-mcp-server/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/rfdez/pvpc-mcp-server

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/rfdez/pvpc-mcp-server/agents-md/github.svg)](https://agentmods.dev/instructions/rfdez/pvpc-mcp-server/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/rfdez/pvpc-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/rfdez/pvpc-mcp-server/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/rfdez/pvpc-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/rfdez/pvpc-mcp-server/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 538 This file is loaded in full into every session.

When invoked 538 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00538	$0.00538
Opus 5.5	$0.00215	$0.00215
Sonnet 5.5	$0.00108	$0.00108
Haiku 4.5	$0.00054	$0.00054

Measured 2mo ago against content hash dc66a972f08b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pvpc-mcp-server AGENTS.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 2mo 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.

AGENTS.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This is AGENTS.md, a README for agents: a dedicated, predictable place to provide the context and instructions to help AI coding agents work on your project.

Do

default to small files and diffs. avoid repo wide rewrites unless asked
use descriptive commit messages
follow the coding style of the project
run tests, linters, and type checkers on changed files
keep changes focused and minimal
explain your reasoning in commit messages or PR descriptions
modify the MCP server version only when necessary, according to semver
keep the server.json file up to date with the latest version of the MCP server

Don't

don't make large speculative changes without confirmation
don't add or remove dependencies without approval
don't change files unrelated to the task
don't ignore linting or type errors
don't leave commented out code or excessive logging

Commands

Note: Always lint, test, and typecheck updated files. Use project-wide build sparingly.

Type check a single file by path: npm exec tsc -- --noEmit path/to/file.ts
Format a single file by path: npm exec prettier -- --write path/to/file.ts
Lint a single file by path: npm exec eslint -- --fix path/to/file.ts
Full build (when explicitly requested): npm run build

Safety and permissions

Allowed without prompt:

read files, list files
tsc single file, prettier, eslint

Ask first:

package installs
git push
deleting files, chmod
running full build

Project structure

src/index.ts - entry point with a small CLI to run the MCP Server using standard input/output transport or HTTP transport depending on the command line arguments
src/mcp.ts - MCP Server implementation
src/pvpc.ts - Class to interact with the esios API

API docs

esios API docs live in https://api.esios.ree.es/
use the Context 7 MCP server to look up docs on the fly

Pull Request checklist

title: feat(scope): short description
format, lint, type check - all green before commit
diff is small and focused. include a brief summary of what changed and why
remove any excessive logs or comments before sending a PR

Read the full file on GitHub · 69 lines

Changes

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.

2mo ago First seen · 69 lines · 538 tokens per session scan A dc66a972f08b

Subscribe to this mod's changes

pvpc-mcp-server AGENTS.md is an instructions file published in the GitHub repository rfdez/pvpc-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 538 tokens to every session, about $0.0022 per session on Opus 5.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.

mcp-server pvpc

pvpc-mcp-server AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pvpc-mcp-server AGENTS.mdrfdez/pvpc-mcp-server	Instructions file	0	2mo ago	MIT	A	538	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

pvpc-mcp-server: Instructions file for Codex