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 skills/jetbrains/mps/mps-ide-pluginnpx skills add JetBrains/MPS --skill mps-ide-plugingit clone --depth 1 https://github.com/JetBrains/MPSWrote 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/skills/jetbrains/mps/mps-ide-plugin)<a href="https://agentmods.dev/skills/jetbrains/mps/mps-ide-plugin"><img src="https://agentmods.dev/badge/skills/jetbrains/mps/mps-ide-plugin.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.00209 | $0.03449 |
| Opus 5 | $0.00105 | $0.01724 |
| Sonnet 5 | $0.00042 | $0.00690 |
| Haiku 4.5 | $0.00021 | $0.00345 |
Grade A, and why
mps-ide-plugin 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MPS IDE Plugin Language
This skill covers IDE plugins: code that integrates with the MPS/IntelliJ host IDE — menu actions, tool windows, shortcuts, settings panels. Plugin code lives in a regular Solution module (compilation mode: "Regular MPS module contributing extensions to MPS") with model(s) using jetbrains.mps.lang.plugin and jetbrains.mps.lang.plugin.standalone. The canonical model name is <solution_name>.plugin — MPS auto-registers it on that convention.
Official documentation: https://www.jetbrains.com/help/mps/plugin.html
Critical Directives
- Disambiguate the overloaded vocabulary first. "Plugin", "tool", "action group" each mean two or three different things. See
references/terminology.mdbefore naming anything. - A plugin solution is NOT an IntelliJ plugin jar. The solution contains MPS models; the jar is what the MPS Build Language packages from it. Don't conflate.
- A
Toolis a tool window — a dockable panel — not a CLI tool or an action. - Use MPS MCP tools for edits.
mps_mcp_insert_root_node_from_json,mps_mcp_update_node,mps_mcp_print_node. Resolve concept names withmps_mcp_search_concepts/mps_mcp_get_concept_details; never guess. ModificationStatement.modifiedGroupis a node reference (r:...), not a concept reference (c:...). Look up the target group viamps_mcp_search_root_node_by_nameto obtain the node ref.- Add a model dependency on
jetbrains.mps.ide.actionsbefore referencing built-in groups (MainMenu,EditorPopup,NodeActions,ModelActions,ModuleActions,MainToolbar,ProjectViewPopupMenu). - Pick
requiredAccessdeliberately:none(no model touch),read(safe traversal),command(mutates with undo + write lock — never open modal dialogs from here),editorCommand(correct undo scope for editor-driven edits). - Don't call
project.tool<…>fromdispose. The lookup can fail during teardown. - Mac keymap trap: with
Keymap = Default, MPS translatesctrl→cmdon macOS. If you specifically wantctrlon Mac, add a separateMac_OS_XKeymapChangesDeclaration. - After edits, rebuild the module (
mps_mcp_alter_nodesMAKE) so generated Java is current, then Reload All in MPS for hot-load. - Validate every new root with
mps_mcp_check_root_node_problems.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/action-groups.md 5.7 KB
- references/actions.md 8.9 KB
- references/common-failures.md 2.0 KB
- references/concept-catalog.md 7.3 KB
- references/editor-tabs.md 4.6 KB
- references/idea-configuration-xml.md 1.1 KB
- references/interface-group.md 2.5 KB
- references/keymaps.md 2.2 KB
- references/lifecycle-plugins.md 2.1 KB
- references/non-dumb-aware.md 887 B
- references/preferences.md 2.8 KB
- references/terminology.md 3.3 KB
- references/tools.md 3.9 KB
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.
- 4d ago First seen · 90 lines · 209 tokens per session scan A fc961af0d677
mps-ide-plugin is a skill published in the GitHub repository JetBrains/MPS (1,658 stars, last pushed today), licensed Apache-2.0. It adds 209 tokens to every session and 3,449 once invoked, about $0.0010 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 skills, from other repositories
langium
A comprehensive skill to understanding how Langium-based projects work — from grammar definition through code generation, runtime parsing, linking, validation, and LSP integration.
lai-gen-evals
Expand and refine the evaluation suite for a Langium DSL project. Generates comprehensive eval files that cover syntactic correctness, semantic validity, user intent matching, edge cases, and language understanding.
lai
Guide for using the langium-ai (LAI) CLI to generate language descriptors, synthesize system prompts, run evaluations, and iteratively refine AI-powered tooling in Langium projects. Use when working with lai commands, descriptors, or evaluation files.
lai-gen-descriptor
Generate or refine a language descriptor for a Langium DSL project. Bootstraps a new descriptor via lai gen descriptor if none exists, then guides refinement of paths, services, examples, documentation, and structure.
lai-gen-mcp
Generate a Model Context Protocol (MCP) server that exposes a Langium DSL's parser and validator as an MCP tool, allowing any MCP-compatible client to validate DSL code and receive diagnostics.
lai-gen-language-skill
Skill for generating a skill for understanding a specific Langium-based DSL. Used in cooperation with the lai & langium skills for understanding.