Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/martoc/mcp-spark-documentation/claude-mdgit clone --depth 1 https://github.com/martoc/mcp-spark-documentationWrote 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/martoc/mcp-spark-documentation/claude-md)<a href="https://agentmods.dev/instructions/martoc/mcp-spark-documentation/claude-md"><img src="https://agentmods.dev/badge/instructions/martoc/mcp-spark-documentation/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.01622 | $0.01622 |
| Opus 5 | $0.00811 | $0.00811 |
| Sonnet 5 | $0.00324 | $0.00324 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
mcp-spark-documentation 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 5d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
This file contains instructions for Claude Code when working with the MCP Spark Documentation Server codebase.
Project Overview
This is an MCP (Model Context Protocol) server that provides search and retrieval tools for Apache Spark documentation. It uses:
- FastMCP for the MCP server framework
- SQLite FTS5 for full-text search with BM25 ranking
- Python-frontmatter for parsing markdown files with YAML frontmatter
- Sparse Git checkout for efficient cloning of the docs directory
Code Principles
British English
- Use British English in all code, comments, and documentation
- Examples: "initialise" not "initialize", "colour" not "color"
Type Safety
- All functions must have type hints
- Use modern union syntax:
str | Noneinstead ofOptional[str] - Run mypy in strict mode before committing
Error Handling
- Use explicit error handling
- Raise appropriate exceptions with descriptive messages
- Never silently fail
Code Style
- Follow PEP 8 guidelines
- Maximum line length: 120 characters
- Use ruff for linting and formatting
- See CODESTYLE.md for detailed style guidelines
Development Workflow
Making Changes
-
Before starting:
- Ensure development environment is initialised:
make init - Understand the existing code structure
- Ensure development environment is initialised:
-
During development:
- Write tests for new functionality
- Update type hints as needed
- Add docstrings following Google style
-
Before committing:
- Format code:
make format - Run linter:
make lint - Run type checker:
make typecheck - Run tests:
make test - Or run all checks:
make build
- Format code:
Testing
- Write tests using pytest
- Place tests in
tests/directory - Mirror source structure in test files
- Test both success and failure cases
- Aim for high coverage (>80%)
Common Tasks
Adding a New Feature
- Update the relevant model in
models.pyif needed - Implement the feature in the appropriate module
- Add corresponding tests
- Update documentation
- Run
make buildto verify all checks pass
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.
- 5d ago First seen · 256 lines · 1,622 tokens per session scan A 884bbd4eb6a0
mcp-spark-documentation CLAUDE.md is an instructions file published in the GitHub repository martoc/mcp-spark-documentation (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,622 tokens to every session, about $0.0081 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
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).
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.
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 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.