Borrowing it
Nothing to install: this file belongs to cahaseler/wikijs-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/cahaseler/wikijs-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/cahaseler/wikijs-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/cahaseler/wikijs-mcp/claude-md)<a href="https://agentmods.dev/instructions/cahaseler/wikijs-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/cahaseler/wikijs-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.00684 | $0.00684 |
| Opus 5 | $0.00342 | $0.00342 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
wikijs-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 — 74 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.
Commands
Build Commands
npm run build- Compiles TypeScript to JavaScript and sets executable permissionsmake build- Alternative build command using Makefilenpm run codegen- Generates TypeScript types from WikiJS GraphQL schema (requires WIKIJS_URL in .env)
Development Commands
make run- Builds and runs the MCP servermake clean- Removes build artifactsdocker-compose up -d- Starts a local WikiJS instance for testingdocker-compose down- Stops the local WikiJS instance
Architecture
This is a Model Context Protocol (MCP) server that bridges AI assistants with WikiJS instances. The architecture follows a three-layer pattern:
Core Components
-
MCP Layer (
src/mcp/)WikiJSMcpServerclass manages the MCP server lifecycle and tool registration- Tools are registered in
src/mcp/index.ts:27-54with specific parameter schemas - Each tool is a separate module in
src/mcp/tools/
-
WikiJS Client Layer (
src/wikijs/)WikiJSClientclass wraps GraphQL operations- Uses generated GraphQL types from
src/wikijs/generated/graphql.ts - GraphQL queries are defined in
src/wikijs/queries/pages.graphql
-
Entry Point (
src/index.ts)- Initializes WikiJS client with URL and API key from environment
- Creates MCP server instance and connects via stdio transport
- Handles fatal errors and process exit
Tool Architecture
Each MCP tool follows a consistent pattern:
- Exports a
createToolfunction that returns a handler - Exports a
PARAMETERSschema for validation - Uses Zod for runtime parameter validation
- Returns structured responses with content arrays
GraphQL Integration
The project uses GraphQL Code Generator to create typed SDK from WikiJS API:
- Schema is fetched from
${WIKIJS_URL}/graphql - Queries in
.graphqlfiles generate TypeScript types - SDK provides type-safe methods for WikiJS operations
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 · 74 lines · 684 tokens per session scan A bc944f174670
wikijs-mcp CLAUDE.md is an instructions file published in the GitHub repository cahaseler/wikijs-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 684 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.