Borrowing it
Nothing to install: this file belongs to pidster/persona-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/pidster/persona-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/pidster/persona-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/pidster/persona-mcp/claude-md)<a href="https://agentmods.dev/instructions/pidster/persona-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pidster/persona-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.00617 | $0.00617 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
persona-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 7d 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 — 90 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 provides LLM clients with specialized prompt personas for improved problem-solving approaches in software development tasks.
Technology Stack
- TypeScript with ES modules
- @modelcontextprotocol/sdk for MCP protocol implementation
- Zod for schema validation
- tsup for building and bundling
Development Commands
npm run build # Build the project with tsup
npm run dev # Watch mode for development
npm run start # Start the MCP server
npm run typecheck # TypeScript type checking
Architecture
Core Components
src/index.ts- Main MCP server entry point with HTTP transportsrc/persona-manager.ts- Manages persona loading and prompt generationsrc/types/- TypeScript type definitions for personas and MCPsrc/personas/- Individual persona definitions
MCP Capabilities
The server exposes:
- Resources: Persona definitions accessible via
persona://{id}URIs - Prompts: Persona adoption prompts via
adopt-persona-{id}commands
Persona System
Each persona includes:
- Unique ID and role classification
- Specialized expertise areas
- Problem-solving approach
- Detailed prompt template
- Examples and tags
Adding New Personas
- Create new persona file in
src/personas/ - Export persona object following the
Personatype - Add to persona imports in
persona-manager.ts - Include in
defaultPersonasarray
Testing
Test the server using MCP Inspector or integrate with MCP-compatible clients like Claude Desktop.
File Organization
- Store plans in a
plans/directory using a file name format{year-month-day}-{version}-{brief topic}.md
Code Guidelines
- Never use emojis in docs unless the user specifically requests it
Automatic Persona Selection
When the Personas MCP server is connected and the user asks a question:
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.
- 7d ago First seen · 90 lines · 617 tokens per session scan A 6fd3337c1228
persona-mcp CLAUDE.md is an instructions file published in the GitHub repository pidster/persona-mcp (5 stars, last pushed 3mo ago), licensed MIT. It adds 617 tokens to every session, about $0.0031 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.