Borrowing it
Nothing to install: this file belongs to ervwalter/mcp-kanka. 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/ervwalter/mcp-kanka/main/CLAUDE.mdgit clone --depth 1 https://github.com/ervwalter/mcp-kankaWrote 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/ervwalter/mcp-kanka/claude-md)<a href="https://agentmods.dev/instructions/ervwalter/mcp-kanka/claude-md"><img src="https://agentmods.dev/badge/instructions/ervwalter/mcp-kanka/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.03011 | $0.03011 |
| Opus 5 | $0.01505 | $0.01505 |
| Sonnet 5 | $0.00602 | $0.00602 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
mcp-kanka 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 — 379 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 the mcp-kanka repository.
Project Overview
This is an MCP (Model Context Protocol) server that provides AI assistants with tools to interact with Kanka campaigns. It exposes 9 tools for CRUD operations on Kanka entities (characters, locations, organizations, etc.) and implements client-side filtering, fuzzy search, and markdown/HTML conversion.
Key Development Commands
This project uses uv for dependency management. All commands are wrapped in the Makefile for convenience:
# Install development environment (uses uv sync)
make install
# Sync dependencies without updating lock file
make sync
# Run tests
make test
# Format code
make format
# Run linting
make lint
# Run type checking
make typecheck
# Run everything (lint + typecheck + tests)
make check
# Generate coverage report
make coverage
# Clean up generated files
make clean
Direct uv commands
# Install dependencies
uv sync --all-groups
# Run a command in the environment
uv run pytest
# Add a new dependency
uv add package-name
# Add a dev dependency
uv add --group dev package-name
# Update dependencies
uv lock --upgrade
# Build the package
uv build
Git Commit Message Format
This project uses conventional commits format:
<type>(<scope>): <subject>
<body>
<footer>
Types:
feat: New featurefix: Bug fixdocs: Documentation only changesstyle: Code style changes (formatting, missing semicolons, etc)refactor: Code change that neither fixes a bug nor adds a featuretest: Adding missing tests or correcting existing testschore: Changes to build process, dependencies, or auxiliary tools
Examples:
feat: add sync/timestamp features and change name filteringfix: correct pagination logic to use SDK propertieschore(deps): update dependency python to v3.13.5refactor: add operations layer for reusable business logic
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 · 379 lines · 3,011 tokens per session scan A af45b80a29b7
mcp-kanka CLAUDE.md is an instructions file published in the GitHub repository ervwalter/mcp-kanka (4 stars, last pushed 5d ago), licensed MIT. It adds 3,011 tokens to every session, about $0.0151 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.