Borrowing it
Nothing to install: this file belongs to yusong652/flac-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/flac-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/yusong652/flac-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/flac-mcp/claude-md)<a href="https://agentmods.dev/instructions/yusong652/flac-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/yusong652/flac-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.01514 | $0.01514 |
| Opus 5 | $0.00757 | $0.00757 |
| Sonnet 5 | $0.00303 | $0.00303 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
flac-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 — 143 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 flac-mcp repository.
Project Overview
flac-mcp provides an MCP server for ITASCA FLAC workflows plus a bridge runtime that runs inside FLAC GUI.
This project spans two runtime contexts:
src/flac_mcp/(Python >= 3.10): MCP server package used by clients/toolingitasca-mcp-bridge/(FLAC embedded Python, often 3.6): WebSocket bridge running inside FLAC GUI — a separate repository (yusong652/itasca-mcp-bridge) vendored here as a git submodule
Treat these as separate deployment targets with independent release cycles.
Core Architecture
MCP side (src/flac_mcp)
- Exposes documentation tools and execution tools through FastMCP
- Communicates with bridge via WebSocket client (
flac_mcp.bridge.client) - Returns a unified tool envelope:
ok,data,error - Dual execution model: synchronous REPL (
flac_execute_code) for quick queries, script-first async (flac_execute_task+flac_check_task_status) for long-running simulations
Bridge side (itasca-mcp-bridge)
- Runs in FLAC GUI process
- Owns thread-safe interaction with ITASCA SDK
- Handles long-running tasks and diagnostics
- Must be started from FLAC GUI (for example with
%run .../itasca-mcp-bridge/start_bridge.py)
Repository Layout
flac-mcp/
├── src/flac_mcp/
│ ├── bridge/ # MCP-side bridge client/task manager
│ ├── knowledge/ # command/API/reference search system
│ ├── tools/ # MCP tool implementations
│ ├── formatting.py # shared response formatting
│ └── server.py # MCP server entrypoint
├── itasca-mcp-bridge/ # git submodule → separate repo; runtime executed inside FLAC GUI
└── tests/ # MCP/tool contract tests
Development Commands
Run from repository root.
uv sync
uv sync --group dev
uv run flac-mcp
uv run pytest tests/test_phase2_tools.py
uv run pytest tests/test_tool_contracts.py
Engineering Rules
- Keep MCP and bridge concerns separate.
- Do not couple MCP logic to FLAC GUI internals.
- Do not introduce application/session policy into bridge runtime.
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 · 143 lines · 1,514 tokens per session scan A b8b46f1675da
flac-mcp CLAUDE.md is an instructions file published in the GitHub repository yusong652/flac-mcp (39 stars, last pushed 2mo ago), licensed MIT. It adds 1,514 tokens to every session, about $0.0076 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.
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.