Borrowing it
Nothing to install: this file belongs to brunopedrazza/pluggy-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.
curl -O https://raw.githubusercontent.com/brunopedrazza/pluggy-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/brunopedrazza/pluggy-mcp-serverWrote 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/brunopedrazza/pluggy-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/brunopedrazza/pluggy-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/brunopedrazza/pluggy-mcp-server/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.00837 | $0.00837 |
| Opus 5 | $0.00418 | $0.00418 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
pluggy-mcp-server 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — pluggy-mcp-server
Guidance for any agent working in this repo. Read DESIGN.md first — every decision and its reasoning lives there, and README.md covers setup and deployment.
What this is
A read-only MCP server over one person's real bank, credit card and investment data (Brazilian Open
Finance, via Pluggy). It cannot move money, and a test fails if anyone imports Pluggy's
PaymentsClient. Keep it that way.
Hard conventions
- English only in repo artifacts: code, comments, docs, commit messages. (Conversations with the owner happen in Portuguese; nothing Portuguese lands in the repo.)
- Never sum rows mentally. Write and run code. A month is hundreds of rows and a quietly wrong total is worse than no answer — the same rule the server injects into its own handshake.
- Amounts are normalised so negative always means money leaving the account, on bank accounts
and cards alike, and always in the account's own currency.
valor_origis for reconciliation only: never sum it, never read it as reais.
Two MCP registrations, and which one to use
Once the server is deployed (README) you have two of it: the one on the VM, and whatever
npm run dev is serving out of your working tree. Register them as separate entries — the
deployed one globally, the local one scoped to this directory — so the split is decided by where
you are rather than by guesswork:
| server | points at | use it for |
|---|---|---|
pluggy |
the VM, running origin/main |
any real question about the owner's finances |
pluggy-dev |
127.0.0.1:8787, this working tree |
exercising a change you are making right now |
pluggy-dev only answers while npm run dev is running, so a ConnectionRefused from it means
the dev server is down, not that anything is broken.
They read the same account with the same credentials, so the numbers are not "test data" — they
are the real numbers, computed by whichever code you happen to be pointing at. Picking pluggy-dev
by accident does not produce an obvious error; it produces a plausible figure from a half-finished
edit. So: pluggy-dev only to verify your own change behaves, pluggy for anything whose answer
the owner might act on.
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 · 70 lines · 837 tokens per session scan A 2c839edc7299
pluggy-mcp-server CLAUDE.md is an instructions file published in the GitHub repository brunopedrazza/pluggy-mcp-server (0 stars, last pushed 11d ago), licensed MIT. It adds 837 tokens to every session, about $0.0042 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.