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/yusong652/itasca-mcp/agents-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/agents-md)<a href="https://agentmods.dev/instructions/yusong652/itasca-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/yusong652/itasca-mcp/agents-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.01234 | $0.01234 |
| Opus 5 | $0.00617 | $0.00617 |
| Sonnet 5 | $0.00247 | $0.00247 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
itasca-mcp AGENTS.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.
Copies of this mod
2 near-identical copies found in the catalogue:
- itasca-mcp GEMINI.md — 92% identical, 7 lines differ
- itasca-mcp CLAUDE.md — 86% identical, 65 lines differ
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.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
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.
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
Repository Layout
itasca-mcp/
├── src/itasca_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/ # submodule → github.com/yusong652/itasca-mcp-bridge
├── addon.py # PFC-side first-install bootstrap (pip-installs the bridge)
└── tests/ # MCP/tool contract tests
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 · 122 lines · 1,234 tokens per session scan A ce8ffc86882d
itasca-mcp AGENTS.md is an instructions file published in the GitHub repository yusong652/itasca-mcp (172 stars, last pushed 7d ago), licensed MIT. It adds 1,234 tokens to every session, about $0.0062 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
yade-mcp AGENTS.md
Instructions for yusong652/yade-mcp, covering agents.md, project overview, build and test, branch strategy and release workflow.
yade-mcp CLAUDE.md
Instructions for yusong652/yade-mcp, covering claude.md, project overview, build and test, branch strategy and release workflow.
bio-gene-to-reference-tree copilot-instructions.md
Copilot instructions for Hongda-Zhao/bio-gene-to-reference-tree, a project described as: Auditable agent skill for resolving protein queries, selecting references, and planning reproducible phylogenetic trees.
braina GEMINI.md
Instructions for brainets/braina, covering project: braina (brain interaction analysis), 1. project context & purpose, 2. commands, verify environment (all core dependencies) and run the verification test suite for frites + hoi.
research-automation CLAUDE.md
Instructions for lucafusarbassini/research-automation, covering ricet - research automation framework, project overview, claude-flow mcp, workflow habits and file organization.
shannon-prover CLAUDE.md
Claude Code instructions for SkyShannonProver/shannon-prover, covering shannon prover: claude entry point, current boundary, easycrypt environment, eval safety and current documentation.