jshell

Instructions for using JShell, Java's interactive read-evaluate-print environment, to run and test Java snippets.

In plain words
What is it for?
Use it for quick Java experiments, scratch code, and interactive checks without creating a full project.
Why use it?
They help ensure JShell uses a working Java installation and that the interactive process is properly tracked until it exits.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/heapy/kortex/jshell
Any agent
npx skills add Heapy/kortex --skill jshell
Clone the repo
git clone --depth 1 https://github.com/Heapy/kortex

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 491 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00491
Opus 5 $0.00012 $0.00246
Sonnet 5 $0.00005 $0.00098
Haiku 4.5 $0.00002 $0.00049

Measured yesterday against content hash bbd745316aa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/kortex/skills/jshell/SKILL.md · 48 lines

What it actually says

JShell

Run JShell in an agent-controlled terminal and own its lifecycle. Record its pid when it starts, keep the terminal session, and do not finish the task until that session has exited.

Resolve the executable

Run jshell --version before the first evaluation. On macOS, /usr/bin/jshell can be a launcher that reports no Java runtime even when an SDK-managed JDK is installed. In that case, resolve an installed JDK and use its absolute bin/jshell path for the rest of the task.

If a requested JShell option is uncertain, inspect that executable's --help or --help-extra.

Start and use JShell

Start this command in a terminal with TTY enabled, replacing the final argument with the resolved absolute path:

/bin/sh -c 'printf "JSHELL_PID=%s\n" "$$" >&2; exec "$1" --execution local --feedback concise' sh /absolute/path/to/jshell

Save both the returned terminal-session id and the printed JSHELL_PID. exec replaces the shell with JShell without changing the pid, while --execution local keeps evaluation in that tracked process.

Send Java snippets to the terminal session with a trailing newline. Poll a running session with an empty write. A returned live-session id only means the command is still running; it does not prove that JShell is waiting at a prompt.

Finish the session

Never send /exit. When no more evaluation is needed:

  1. From a separate terminal command, send TERM to the recorded numeric pid. For example, if JShell printed JSHELL_PID=16438, run kill -TERM 16438.
  2. Poll the original terminal session with empty writes for at most five seconds.
  3. If it has not exited after those five seconds, confirm that the same pid is still the tracked JShell process, send KILL to that pid, and poll the original session again until it exits.

Never abandon a live JShell terminal session. Do not use pkill jshell or killall; terminate only the pid recorded for the current task.

Files

What ships with it

1 file 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.

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.

  1. yesterday First seen · 48 lines · 24 tokens per session scan A bbd745316aa5

Subscribe to this mod's changes

jshell is a skill published in the GitHub repository Heapy/kortex (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 24 tokens to every session and 491 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

mobile-experience-report

Use when the user says 'my site looks bad on mobile', 'check mobile layout', 'responsive audit', or 'site broken on phones'. Diagnoses breakpoint problems, text sizing, column stacking failures, hidden elements, and navigation menu behavior, device by device.

respira-press/agent-skills-wordpress · 58 tokens

motherduck-design-dive

Design or redesign a MotherDuck Dive as a responsive, reusable analytics interface. Use when a Dive must be mobile-friendly from the start, support light and dark modes, reserve space for filters, use restrained Power BI-style information design, embed small charts inside metric components, or work across customers…

motherduckdb/agent-skills · 69 tokens

desktop-expert

Compose Multiplatform Desktop patterns for the desktopApp/ module. Use when working with (1) Desktop-only APIs (Window, WindowState, Tray, MenuBar, Dialog), (2) keyboard shortcuts and menu systems with OS-aware conventions (Cmd vs Ctrl, isMacOS branching), (3) desktop navigation (NavigationRail/sidebar vs Android…

vitorpamplona/amethyst · 157 tokens

gradle-expert

Build optimization, dependency resolution, and multi-module KMP troubleshooting for AmethystMultiplatform. Use when working with: (1) Gradle build files (build.gradle.kts, settings.gradle), (2) Version catalog (libs.versions.toml), (3) Build errors and dependency conflicts, (4) Module dependencies and source sets, (5)…

vitorpamplona/amethyst · 132 tokens

add-native

Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps…

microsoft/power-platform-skills · 96 tokens

amy-expert

Patterns for extending amy, the Amethyst CLI in cli/. Use when adding an amy command, touching files under cli/src/main/kotlin/…/cli/, wiring a new subcommand into Main.kt, writing an interop test script that drives Amy, or extracting logic out of amethyst/ into commons/ so a CLI command can call it. Enforces the…

vitorpamplona/amethyst · 217 tokens