Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/wgdevelopment/ynab-mcp-server/claude-mdgit clone --depth 1 https://github.com/WGDevelopment/ynab-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/wgdevelopment/ynab-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/wgdevelopment/ynab-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/wgdevelopment/ynab-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 | $0.00911 | $0.00911 |
| Opus 5 | $0.00456 | $0.00456 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
ynab-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 3d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YNAB MCP Server - Claude Code Context
Project Overview
A minimal, auditable MCP (Model Context Protocol) server for YNAB budget management. Designed for local AI assistants that need to read and modify YNAB budgets while keeping sensitive financial context local.
Architecture
src/ynab_mcp_server/
__init__.py # Package initialization
api.py # YNAB API client (~300 lines, all network communication)
models.py # Pydantic models for YNAB data structures
server.py # MCP server implementation with tool handlers
Key Components
- api.py: All YNAB API communication goes through here. Single endpoint:
https://api.ynab.com/v1 - server.py: MCP tool definitions and handlers. Entry point via
ynab-mcp run - models.py: Type-safe Pydantic models for budgets, accounts, categories, transactions
Security Considerations
Token Handling
- YNAB Personal Access Token stored in OS keyring (recommended) or environment variable
- Token retrieved at runtime via
keyringlibrary orYNAB_API_TOKENenv var - NEVER log tokens - audit api.py for any logging statements
Data Flow
- Local: User goals, AI coaching responses, conversation history, life context
- To YNAB API: Only structured API calls (get categories, create transaction, etc.)
Audit Points
When reviewing changes, check:
api.py- All network calls, ensure no token leakage- Error handlers - Should not expose sensitive data
- Logging statements - Should not include tokens or financial details
Development
Setup
# Create virtual environment
python -m venv .venv
source .venv/bin/activate # or .venv\Scripts\activate on Windows
# Install with dev dependencies
pip install -e .[dev]
Testing
pytest -v
pytest --cov=src/ynab_mcp_server # with coverage
Linting
pip install ruff
ruff check src/
ruff format src/
CI/CD
Comprehensive quality gates run on all PRs:
- Tests: Python 3.10, 3.11, 3.12 matrix with coverage
- Semgrep: SAST scanning (security-audit, OWASP, Python, secrets)
- pip-audit: Dependency vulnerability scanning
- Linting: Ruff + Super-Linter (YAML, Markdown, Shell)
- Type Checking: mypy
- Claude Review: AI code review after all gates pass
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.
- 3d ago First seen · 110 lines · 911 tokens per session scan A 1af74b71e417
ynab-mcp-server CLAUDE.md is an instructions file published in the GitHub repository WGDevelopment/ynab-mcp-server (0 stars, last pushed 7mo ago), licensed MIT. It adds 911 tokens to every session, about $0.0046 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-09-01.
Other instructions, from other repositories
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.