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/jonasklimt/ie_mcp/copilot-instructionsgit clone --depth 1 https://github.com/JonasKlimt/ie_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/jonasklimt/ie_mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/jonasklimt/ie_mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jonasklimt/ie_mcp/copilot-instructions.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 | $0.01439 | $0.01439 |
| Opus 5 | $0.00720 | $0.00720 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
ie_mcp 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 3d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for ie-mcp
These instructions apply whenever you are working in this repository or using the ie-mcp MCP server from any workspace.
Automatic ie-mcp usage for tracked packages
If the user asks about any package that is tracked by this server, or if the current question/code clearly concerns a tracked package, use the ie-mcp MCP tools by default even when the user did not explicitly ask to use ie-mcp.
Do not wait for explicit user wording such as "use ie-mcp" when package intent is already clear from the question or code context.
Keyword routing map (automatic triggers)
If trigger terms appear in the user request, code context, stack traces, or variable names, route via ie-mcp automatically.
-
Core Brightway LCA workflow
- Triggers:
LCA,life cycle assessment,LCI,LCIA,activity,activities,exchange,exchanges,biosphere,technosphere,inventory,database,functional unit,characterization,impact assessment,impact category,normalization,weighting,allocation,system boundary,contribution analysis,hotspot - Check first:
brightway25(orbrightway2for legacy), thenbw2data,bw2calc,bw2io,bw2analyzer
- Triggers:
-
Scenario / prospective LCA
- Triggers:
prospective,scenario,future,IAM,transformation,premise,wurst,pathway - Check first:
premise,wurst,pathways,randonneur,randonneur_data,ecoinvent_migrate
- Triggers:
-
Temporal / dynamic LCA
- Triggers:
dynamic LCA,time-dependent,temporal,timeline,dynamic characterization,time-explicit - Check first:
bw_temporalis,bw_timex,dynamic_characterization
- Triggers:
-
Regionalized / spatial LCA
- Triggers:
regionalized,spatial,location-specific,region,geo - Check first:
brightway2_regional,simple_regional,regioinvent,edges
- Triggers:
-
IO / hybrid / MRIO workflows
- Triggers:
MRIO,EXIOBASE,input-output,hybrid LCA,footprint,trade-embodied - Check first:
pymrio,bw_exiobase,brightway_hybrid,mrio_common_metadata
- Triggers:
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.
- 3d ago First seen · 133 lines · 1,439 tokens per session scan A 147f117f1f94
ie_mcp copilot-instructions.md is an instructions file published in the GitHub repository JonasKlimt/ie_mcp (3 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 1,439 tokens to every session, about $0.0072 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-31.
Other instructions, from other repositories
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
flyto-core CLAUDE.md
Claude Code instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.