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/stepfunctionllc/mcp-server-cantera/copilot-instructionsgit clone --depth 1 https://github.com/StepFunctionLLC/mcp-server-canteraWhat 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 | $0.01025 | $0.01025 |
| Opus 5 | $0.00513 | $0.00513 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
mcp-server-cantera copilot-instructions.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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-server-cantera Copilot Instructions
This repository implements a Model Context Protocol (MCP) server integration for Cantera, enabling LLMs to perform chemical kinetics and thermodynamic calculations.
Architecture & Code Structure
- Core Logic: The entire server implementation resides in
src/mcp_server_cantera/server.py. - Framework: Uses FastMCP for clean, decorator-based tool definitions with Pydantic validation.
- Mechanism Discovery: The
mechanisms/directory at the project root stores custom.yamlmechanism files.- The server dynamically locates this folder via
get_custom_mechanisms_dir(). resolve_mechanism()handles the logic to prefer custom mechanisms over built-ins.
- The server dynamically locates this folder via
- Package Layout: Standard
src/layout withpyproject.tomlconfiguration.
Key Developer Workflows
Environment & Installation
- Package Manager: Uses
uvfor fast dependency resolution. - Installation:
uv pip install -e .(Editable install is CRITICAL for mechanism discovery to work). - Python Version: Requires Python 3.10+.
Running the Server
# Run via CLI entry point
mcp-server-cantera
# Or via uv directly
uv run mcp-server-cantera
Testing
- Framework:
pytest - Location:
tests/ - Run tests:
uv run pytest
Coding Conventions
Cantera Usage Support
- Mechanism Loading: Always use
resolve_mechanism(mech_name)before passing toct.Solution(). - State Setting: Prefer
gas.TPX = T, P, Xorgas.TP = T, Pfor setting states. - Units:
- Temperature: Kelvin
- Pressure: Pascals (Code may output bar for readability, but inputs/internal are Pa)
- Energy: J or kJ (be explicit in output strings)
Pydantic Models for Tool Inputs
All tool inputs use Pydantic models for validation. Key models defined in server.py:
GasStateInput: mechanism, temperature, pressure, compositionEquilibriumInput: extends GasStateInput with equilibrium basisCombustionInput: fuel/oxidizer combustion setupSpeciesInput: species property lookupMechanismInput: single mechanism parameter
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.
- yesterday First seen · 112 lines · 1,025 tokens per session scan A a83f6915a39f
mcp-server-cantera copilot-instructions.md is an instructions file published in the GitHub repository StepFunctionLLC/mcp-server-cantera (4 stars, last pushed 2d ago), licensed MIT. It adds 1,025 tokens to every session, about $0.0051 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-09-01.
Other instructions, from other repositories
VCVio AGENTS.md
Instructions for Verified-zkEVM/VCVio, covering vcvio — ai agent guide, fast start, attribution, headers, and docstrings, module scopes and what this project is.
oci-agent CLAUDE.md
Instructions for Netflix-Skunkworks/oci-agent, covering observational causal inference (oci) agent and rules.
bio-gene-to-reference-tree copilot-instructions.md
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.