A status command for checking whether a JetBrains IDE—such as IntelliJ IDEA, WebStorm, or PyCharm—is connected through MCP, and whether tool calls are being redirected to it.

Checking the active IDE and routing prefix, confirming MCP connectivity, and reporting the connected project root and modules when available.

It shows whether IDE routing is active and distinguishes an unavailable connection from a failed MCP request or a deliberately disabled hook.

status — Skill for Claude Code by V-Songbird

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add V-Songbird/slag

Claude Code

/plugin install jetbrains-router

Made for: Claude Code.

Or install jetbrains-router, the plugin that ships this one along with the rest of its 2 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/v-songbird/slag/status.svg)](https://agentmods.dev/skills/v-songbird/slag/status)

Your own site

<a href="https://agentmods.dev/skills/v-songbird/slag/status"><img src="https://agentmods.dev/badge/skills/v-songbird/slag/status.svg" alt="Measured on agentmods" height="20"></a>

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 619 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00085	$0.00619
Opus 5	$0.00043	$0.00309
Sonnet 5	$0.00017	$0.00124
Haiku 4.5	$0.00009	$0.00062

Measured 7d ago against content hash 7c30b4519851, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

status 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 7d 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.

jetbrains-router/skills/status/SKILL.md · 37 lines

What it actually says

jetbrains-status

Gather and report the current jetbrains-router state. Do both probes before replying.

Hook probe — invoke Bash with description: "Probe jetbrains-router state" and command:
```
node "${CLAUDE_PLUGIN_ROOT}/hooks/jb-lib.js" --probe
```
Prints JSON: enforcing (will the hook redirect), prefix (detected/overridden IDE prefix), disabled (kill-switched via JETBRAINS_ROUTER_DISABLE=1), forced, bypass (per-tool bypass list). Exit 0 = enforce, 1 = fail open.
MCP connectivity — check whether any mcp__<prefix>__* tool is registered in this session (match the probe's prefix first, then any of webstorm/rider/idea/pycharm/phpstorm/goland/rubymine/clion/rustrover/datagrip/aqua). If one is, call get_project_modules on it (no arguments). If none is registered, note "MCP tools unavailable". If the call errors, note "MCP call failed" with the error text.
Report — under 10 lines:
- Status — "connected" / "not connected (no MCP tool)" / "not connected (MCP call failed)" / "kill-switched".
- Active IDE + prefix — from the probe (JETBRAINS_MCP_PREFIX override noted if set).
- Project root / modules — from the MCP response, if available.
- Routing state — cross-reference the probes:
  - MCP connected + enforcing: true → routing active (hook redirects Read/Grep/Glob/Edit/Write/Bash/PowerShell)
  - MCP connected + disabled: true → kill-switched (unset JETBRAINS_ROUTER_DISABLE to re-enable)
  - MCP unavailable + enforcing: true → routing will misfire (hook enforces but MCP tools are missing — check IDE → Settings → Tools → MCP Server)
  - MCP unavailable + enforcing: false → routing inactive (native tools in use)

No recommendations beyond the mismatch hints above. The user runs this to verify the plugin is live.

Changes

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.

7d ago First seen · 37 lines · 85 tokens per session scan A 7c30b4519851

Subscribe to this mod's changes

status is a skill published in the GitHub repository V-Songbird/slag (1 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 619 once invoked, about $0.0004 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.

Debugging

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens