yade-mcp: Instructions file for Claude Code

CLAUDE.md

yade-mcp CLAUDE.md is an instructions file for Claude Code from yusong652/yade-mcp. It costs 706 tokens per session, scanned A, original, MIT.

Instructions for YADE MCP, a server that connects AI agents to YADE, an open-source discrete element method engine for simulating collections of particles. The repository contains the server and an HTTP bridge in one monorepo, meaning one repository holds multiple related packages.

In plain words
What is it for?
Developing and testing YADE documentation and execution tools, the bridge, and the package release workflow.
Why use it?
They record the build, test, lint, branch, and release rules needed to work on both packages correctly.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is yusong652/yade-mcp's own configuration. It tells Claude Code how to work on yade-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything yade-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to yusong652/yade-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.

Copy the file
curl -O https://raw.githubusercontent.com/yusong652/yade-mcp/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/yusong652/yade-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for yade-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yusong652/yade-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/yusong652/yade-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/yusong652/yade-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/yusong652/yade-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for yade-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/yusong652/yade-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/yusong652/yade-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 706 This file is loaded in full into every session.
When invoked 706 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00706 $0.00706
Opus 5 $0.00353 $0.00353
Sonnet 5 $0.00141 $0.00141
Haiku 4.5 $0.00071 $0.00071

Measured 9d ago against content hash 155cd0dce73f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

yade-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 9d 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.

CLAUDE.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Project overview

yade-mcp is an MCP server that connects AI agents to YADE (open-source DEM engine). Two packages live in this monorepo:

  • yade-mcp (src/yade_mcp/) — MCP server with 7 tools (2 doc + 5 execution)
  • yade-mcp-bridge (yade-mcp-bridge/) — HTTP + SSE bridge running inside YADE process (zero runtime deps)

Build and test

uv sync --group dev                    # install dependencies
uv run ruff check src/                 # lint MCP server
uv run ruff check yade-mcp-bridge/src/ # lint bridge (uses bridge's own ruff config)
uv run ruff format src/                # format
uv run mypy src/yade_mcp/              # type check
uv run pytest tests/ -v --ignore=tests/test_tools_integration.py  # unit + protocol tests (no YADE needed)
uv run pytest tests/ -v                # all tests (integration tests need YADE + bridge)

Branch strategy

  • master — code only, kept lightweight
  • assets — large binary files (header.gif, header.blend, generation scripts)

Do NOT commit large files (images, .blend, etc.) to master.

Release workflow

Tag-based via GitHub Actions:

  • v* tags → publish yade-mcp to PyPI (e.g., git tag -a v0.1.3 -m "...")
  • bridge-v* tags → publish yade-mcp-bridge to PyPI (e.g., git tag -a bridge-v0.1.1 -m "...")

Both use trusted publishing (PyPI OIDC). Version is defined in __init__.py of each package.

Coding conventions

  • Ruff for linting and formatting (N818: exception names must end with Error)
  • Bridge has its own ruff config in yade-mcp-bridge/pyproject.toml (targets py38, ignores UP032/SIM115)
  • Transport: bridge is stdlib HTTP + SSE (sync, thread-per-request, zero deps); MCP client is async (httpx) — POST per command, one long-lived SSE stream for task-status doorbells
  • Response envelope: all tools return via build_ok() / build_error() from contracts.py

Test structure

  • tests/ — MCP server unit tests (config, contracts, formatting, search)
  • tests/bridge/ — Bridge unit + protocol tests (no YADE runtime needed)
    • test_helpers.py, test_signals.py, test_utils.py, test_execution.py, test_tasks.py — unit tests
    • test_handlers.py — handler tests with mock context
    • test_protocol.py — real HTTP server, tests message format and routing
  • tests/test_bridge_client.py — MCP bridge client (needs running bridge)
  • tests/test_tools_integration.py — end-to-end MCP tools (needs YADE + bridge)

Read the full file on GitHub · 58 lines

Changes

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.

  1. 9d ago First seen · 58 lines · 706 tokens per session scan A 155cd0dce73f

Subscribe to this mod's changes

yade-mcp CLAUDE.md is an instructions file published in the GitHub repository yusong652/yade-mcp (13 stars, last pushed 12d ago), licensed MIT. It adds 706 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens