Borrowing it
Nothing to install: this file belongs to czottmann/kagi-ken-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/czottmann/kagi-ken-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/czottmann/kagi-ken-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/czottmann/kagi-ken-mcp/agents-md)<a href="https://agentmods.dev/instructions/czottmann/kagi-ken-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/czottmann/kagi-ken-mcp/agents-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.00696 | $0.00696 |
| Opus 5 | $0.00348 | $0.00348 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
kagi-ken-mcp AGENTS.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 6d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to LLM agents when working with code in this repository.
Common Commands
Development
npm install # Install dependencies
npm start # Run the MCP server
npm run dev # Run with Node.js inspector for debugging
Testing & Debugging
npx @modelcontextprotocol/inspector node src/index.js # Launch MCP Inspector at localhost:5173
Architecture Overview
This is a Model Context Protocol (MCP) server that provides Kagi search and summarization tools to Claude Desktop/Code. The server acts as a bridge between Claude and the kagi-ken package for accessing Kagi's APIs.
Core Architecture Pattern
MCP Server Structure: The main server (src/index.js) uses the @modelcontextprotocol/sdk to create an MCP server that registers tools and handles communication via stdio transport.
Tool-Based Architecture: Each capability is implemented as a separate MCP tool:
kagi_search_fetch- Multi-query concurrent searchkagi_summarizer- URL/content summarization
Token Resolution System: Authentication follows the same pattern as kagi-ken-cli with priority-based token resolution:
KAGI_SESSION_TOKENenvironment variable~/.kagi_session_tokenfile
Key Components
src/index.js - Main server class that:
- Creates McpServer instance
- Registers tools with Zod schemas for input validation
- Sets up stdio transport and error handling
src/tools/ - Tool implementations:
- Each tool exports both the handler function and config object
- Handlers return MCP-compliant response format with
contentarray - Input validation uses direct Zod schema objects (not
z.object())
src/utils/auth.js - Token resolution that mirrors kagi-ken-cli:
resolveToken()- Priority-based token resolutionreadTokenFromFile()- File-based token reading- Comprehensive error messages for missing tokens
src/utils/formatting.js - Result formatting:
formatSearchResults()- Matches official Kagi MCP output formatgetEnvironmentConfig()- Unified config with token resolution
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.
- 6d ago First seen · 84 lines · 696 tokens per session scan A ccd5ea29ec78
kagi-ken-mcp AGENTS.md is an instructions file published in the GitHub repository czottmann/kagi-ken-mcp (41 stars, last pushed 6mo ago), licensed MIT. It adds 696 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-30.
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.