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/gradusnikov/eclipse-chatgpt-plugin/eclipse-runnpx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-rungit clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-pluginWrote 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/gradusnikov/eclipse-chatgpt-plugin/eclipse-run)<a href="https://agentmods.dev/skills/gradusnikov/eclipse-chatgpt-plugin/eclipse-run"><img src="https://agentmods.dev/badge/skills/gradusnikov/eclipse-chatgpt-plugin/eclipse-run.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.00029 | $0.00757 |
| Opus 5 | $0.00015 | $0.00378 |
| Sonnet 5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
eclipse-run 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Java Applications in Eclipse
Launch Java applications using Eclipse's launch infrastructure. Applications run inside Eclipse with full classpath resolution.
Tools
-
runJavaApplication — Launch a Java app in run mode.
projectName— Eclipse project namemainClass— Fully qualified main class (e.g.,com.example.Main)programArgs— Optional program argumentsvmArgs— Optional JVM arguments (e.g.,-Xmx512m -Dfoo=bar)timeout— Seconds to wait for completion.0= launch in background without waiting. Default:30
-
launchConfiguration — Launch an existing saved launch configuration by name, exactly as it would run from the Run/Debug Configurations dialog. Reuses the configuration's full setup (classpath, VM args, environment variables, working directory, JRebel/agent settings) instead of building a throwaway one.
configurationName— Exact name of the saved configuration (uselistLaunchConfigurationsto find it)mode—runordebug. Default:runtimeout— Seconds to wait for completion.0= background. Default:0
-
listLaunchConfigurations — List saved launch configurations (name, type, and project/main class for Java apps). Use this to discover the exact name for
launchConfiguration. -
stopApplication — Terminate a running application by name/class substring match.
nameOrClass— Substring to match (case-insensitive) against launch name or main class
-
listActiveLaunches — Show all currently running/debugging sessions with status.
-
getConsoleOutput — Read output from Eclipse consoles (use after background launches).
Examples
Run and capture output:
runJavaApplication(projectName="myapp", mainClass="com.example.Main", timeout="30")
Run in background:
runJavaApplication(projectName="myapp", mainClass="com.example.Server", timeout="0")
Run with arguments:
runJavaApplication(projectName="myapp", mainClass="com.example.CLI", programArgs="--verbose input.txt", vmArgs="-Xmx1g")
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 · 68 lines · 29 tokens per session scan A e3b8bfbd15e2
eclipse-run is a skill published in the GitHub repository gradusnikov/eclipse-chatgpt-plugin (167 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 757 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-30.
Other skills, from other repositories
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
investigate-issue
Investigate a GitHub issue by fetching details, analyzing the codebase, researching documentation, and presenting an actionable implementation plan with test guidance. Use when asked to investigate, analyze, triage, or plan work for a GitHub issue. Invoked with /investigate-issue or /investigate-issue (prompts for ID).
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
resolve-pr-comments
Skill "resolve-pr-comments" from maximhq/bifrost, covering resolve pr comments, usage, workflow overview, step 1: detect repository and step 2: fetch unresolved comments (graphql).