Borrowing it
Nothing to install: this file belongs to ddoriboo/pension-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/ddoriboo/pension-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ddoriboo/pension-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/ddoriboo/pension-mcp/claude-md)<a href="https://agentmods.dev/instructions/ddoriboo/pension-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ddoriboo/pension-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.00706 | $0.00706 |
| Opus 5 | $0.00353 | $0.00353 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
pension-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 8d 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 — 92 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.
Project Overview
This is an MCP (Model Context Protocol) server that integrates with Korea's Financial Supervisory Service (FSS) pension portal APIs. It provides access to 12 different pension-related APIs for collecting and analyzing Korean pension data, including pension savings, retirement pensions, and pension statistics.
Core Commands
Running the Server
python fss_pension_mcp_server/fss_pension_server.py
Installing Dependencies
pip install -r fss_pension_mcp_server/requirements.txt
Testing the Server
python fss_pension_mcp_server/test_server.py
Demo Client
python fss_pension_mcp_server/demo_client.py
Architecture
Main Components
-
FSSPensionServer Class (
fss_pension_server.py:40-231)- Core server class that handles all FSS API interactions
- Manages async HTTP client for API calls
- Handles XML/JSON response parsing with xmltodict
-
MCP Server Integration (
fss_pension_server.py:230-580)- Uses
mcp.serverframework for protocol compliance - Implements 14 tools (12 basic APIs + 2 advanced analysis functions)
- Handles tool registration and execution
- Uses
-
API Endpoints
- 12 FSS OpenAPI endpoints for different pension data types
- Base URL:
https://apis.data.go.kr/1160100/service - Requires service key from Korean government data portal
-
Advanced Analysis Functions
analyze_pension_performance(): Multi-API data analysisgenerate_pension_recommendation(): Personalized pension advice
Key Dependencies
mcp==1.0.0- Model Context Protocol frameworkhttpx==0.27.0- Async HTTP client for API callsxmltodict>=0.13.0- XML to dict conversion for API responsespandas>=2.1.4- Data manipulation for analysis functions
API Configuration
Service Key Setup
The server requires a valid service key from Korea's public data portal (data.go.kr):
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.
- 8d ago First seen · 92 lines · 706 tokens per session scan A 003d161674ed
pension-mcp CLAUDE.md is an instructions file published in the GitHub repository ddoriboo/pension-mcp (0 stars, last pushed 1y ago), licensed MIT. It adds 706 tokens to every session, about $0.0035 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
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.
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).
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).
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.
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.