Borrowing it
Nothing to install: this file belongs to yusong652/itasca-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/yusong652/itasca-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/yusong652/itasca-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/yusong652/itasca-mcp/claude-md)<a href="https://agentmods.dev/instructions/yusong652/itasca-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/yusong652/itasca-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.02339 | $0.02339 |
| Opus 5 | $0.01170 | $0.01170 |
| Sonnet 5 | $0.00468 | $0.00468 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
itasca-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.
This is a copy
86% identical to itasca-mcp AGENTS.md — 65 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for coding agents working in the itasca-mcp repository.
Project Overview
itasca-mcp provides an MCP server for ITASCA PFC workflows. The bridge runtime that runs inside PFC GUI lives in the itasca-mcp-bridge repo and is consumed here as a git submodule.
This repository has two runtime contexts:
src/itasca_mcp/(Python >= 3.10): MCP server package used by clients/toolingitasca-mcp-bridge/(submodule, PFC embedded Python often 3.6): HTTP bridge running inside PFC GUI
Treat these as separate deployment targets. End users get the bridge from PyPI (pip install itasca-mcp-bridge): first install happens via the agentic bootstrap's terminal pip step or addon.py, and from then on itasca_mcp_bridge.start() self-upgrades on every start. The submodule exists only so contributors can edit bridge code alongside MCP code without two clones.
The legacy pfc-mcp-bridge PyPI package (last release bridge-v0.3.3) is deprecated and no longer maintained — its code lived in pfc-mcp-bridge/ here and was removed when the submodule replaced it.
Core Architecture
MCP side (src/itasca_mcp)
- Exposes documentation tools and execution tools through FastMCP
- Communicates with bridge via HTTP client (
itasca_mcp.bridge.client) - Returns a unified tool envelope:
ok,data,error - Dual execution model: synchronous REPL (
itasca_execute_code) for quick queries, script-first async (itasca_execute_task+itasca_check_task_status) for long-running simulations
Bridge side (itasca-mcp-bridge submodule)
- Runs in PFC GUI process
- Owns thread-safe interaction with ITASCA SDK
- Handles long-running tasks and diagnostics
- Started inside PFC GUI via
itasca_mcp_bridge.start(), which self-upgrades from PyPI first (best-effort);addon.pyremains the manual first-install bootstrap - The submodule pin in this repo controls which bridge revision contributors develop against; runtime users always get whatever is on PyPI
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 · 183 lines · 2,339 tokens per session scan A d7731910371a
itasca-mcp CLAUDE.md is an instructions file published in the GitHub repository yusong652/itasca-mcp (174 stars, last pushed yesterday), licensed MIT. It adds 2,339 tokens to every session, about $0.0117 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to itasca-mcp AGENTS.md, differing in 65 lines, and is treated as a copy.
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.