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/calebl/ynab-mcp-server/claude-mdgit clone --depth 1 https://github.com/calebl/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/calebl/ynab-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/calebl/ynab-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/calebl/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.00819 | $0.00819 |
| Opus 5 | $0.00409 | $0.00409 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Development Commands
npm install # Install dependencies
npm run build # Compile TypeScript to ./dist
npm start # Start the server
npm run watch # Development build with file watching
npm run debug # Debug with MCP inspector
npm test # Run tests
npm run test:watch # Run tests with file watching
npm run test:coverage # Run tests with coverage report
Git Best Practices
ALWAYS use conventional commits format (Refer to https://www.conventionalcommits.org/en/v1.0.0/) when creating git commit messages.
Architecture Overview
This is a Model Context Protocol (MCP) server that provides AI tools for interacting with YNAB (You Need A Budget) budgets. Built with @modelcontextprotocol/sdk.
Core Structure
- Entry Point:
src/index.ts- Server setup and tool registration - Tools:
src/tools/*.ts- Each tool is a separate module exportingname,description,inputSchema, andexecutefunction - Tests:
src/tests/*.test.ts- Vitest tests for each tool
Tool Module Pattern
Each tool in src/tools/ exports:
name: Tool identifier (snake_case)description: Tool descriptioninputSchema: Zod schema object for input validationexecute(input, api): Async handler receiving input and YNAB API client
Tools are registered in src/index.ts which passes the shared YNAB api instance to each handler.
Environment Variables
YNAB_API_TOKEN(required) - Personal Access Token from YNAB APIYNAB_BUDGET_ID(optional) - Default budget ID
Adding New Tools
- Create
src/tools/MyTool.ts:
import { z } from "zod";
import * as ynab from "ynab";
export const name = "my_tool";
export const description = "What this tool does";
export const inputSchema = {
budgetId: z.string().optional().describe("Budget ID (optional, uses YNAB_BUDGET_ID env var if not provided)"),
requiredParam: z.string().describe("Description of required param"),
};
interface MyToolInput {
budgetId?: string;
requiredParam: string;
}
export async function execute(input: MyToolInput, api: ynab.API) {
try {
const budgetId = input.budgetId || process.env.YNAB_BUDGET_ID;
if (!budgetId) throw new Error("No budget ID provided");
const result = await api.someMethod(budgetId, input.requiredParam);
return {
content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }]
};
} catch (error) {
return {
content: [{ type: "text" as const, text: `Error: ${error instanceof Error ? error.message : 'Unknown error'}` }]
};
}
}
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.
- 4d ago First seen · 97 lines · 819 tokens per session scan A a05883b08b74
ynab-mcp-server CLAUDE.md is an instructions file published in the GitHub repository calebl/ynab-mcp-server (141 stars, last pushed 8mo ago), licensed MIT. It adds 819 tokens to every session, about $0.0041 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-30.
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.