Borrowing it
Nothing to install: this file belongs to zenml-io/mcp-zenml. 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/zenml-io/mcp-zenml/main/CLAUDE.mdgit clone --depth 1 https://github.com/zenml-io/mcp-zenmlWrote 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/zenml-io/mcp-zenml/claude-md)<a href="https://agentmods.dev/instructions/zenml-io/mcp-zenml/claude-md"><img src="https://agentmods.dev/badge/instructions/zenml-io/mcp-zenml/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.04968 | $0.04968 |
| Opus 5 | $0.02484 | $0.02484 |
| Sonnet 5 | $0.00994 | $0.00994 |
| Haiku 4.5 | $0.00497 | $0.00497 |
Grade A, and why
mcp-zenml CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://raw.githubusercontent.com/modelcontextprotocol/registry/main/pkg/model/constants.go | grep CurrentSchemaVersion How it starts
The opening of the file, as written. The whole thing — 397 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
Testing and Development
- Run smoke tests:
uv run scripts/test_mcp_server.py server/zenml_server.py - Run analytics tests:
uv run scripts/test_analytics.py --full-diagnostic - Run unit tests:
uv run scripts/test_datetime_normalization.py - Format code:
./scripts/format.sh(uses ruff for linting/formatting + ty for type checking) - Run MCP server locally:
uv run server/zenml_server.py - Type check only:
uvx ty check(runs type checking without formatting) - Check PEP 723 dependency drift:
python scripts/check_pep723_requirements.py - Validate hashed requirements:
uv pip install --dry-run --require-hashes -r requirements.txtinside an active virtualenv (CI creates a throwaway Python 3.12 environment under the runner temp directory for this check) - Run workflow security scan:
GH_TOKEN=$(gh auth token) uvx zizmor==1.25.2 --format=github --config=.github/zizmor.yml .github/workflows/
Code Quality
- Format + Type Check:
bash scripts/format.sh(runs ruff + ty) - Type Check Only:
uvx ty check(uses configuration frompyproject.toml) - Recompile requirements:
uv pip compile --generate-hashes --exclude-newer "7 days" --python-version 3.12 requirements.in -o requirements.txt - Check PEP 723 dependency drift: use the canonical command listed under Testing and Development above.
- Validate hashed requirements:
uv pip install --dry-run --require-hashes -r requirements.txtinside an active virtualenv
Development Workflow
IMPORTANT: Always use feature branches and pull requests for changes.
ALSO IMPORTANT: Before opening a PR or making a large commit, always run /simplify to review changed code for reuse opportunities, quality issues, and efficiency improvements. Fix any issues it finds before committing.
- Create a feature branch for any changes:
git checkout -b feature/your-feature-name
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 · 397 lines · 4,968 tokens per session scan A b25ddcee6067
mcp-zenml CLAUDE.md is an instructions file published in the GitHub repository zenml-io/mcp-zenml (49 stars, last pushed 14d ago), licensed MIT. It adds 4,968 tokens to every session, about $0.0248 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.