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-testnpx skills add gradusnikov/eclipse-chatgpt-plugin --skill eclipse-testgit clone --depth 1 https://github.com/gradusnikov/eclipse-chatgpt-pluginWhat 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.00031 | $0.00977 |
| Opus 5 | $0.00015 | $0.00489 |
| Sonnet 5 | $0.00006 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
eclipse-test 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests & Build in Eclipse
Execute JUnit tests and Maven builds using Eclipse's built-in infrastructure.
Test Tools
- runAllTests — Run all tests in a project. Provide
projectNameand optionaltimeout(default: 60s). - runPackageTests — Run tests in a specific package. Provide
projectNameandpackageName. - runClassTests — Run all tests in a specific test class. Provide
projectNameandclassName(fully qualified). - runTestMethod — Run a single test method. Provide
projectName,className, andmethodName. - findTestClasses — Find and classify tests as plain JUnit or PDE harness tests. PDE tests must use the
*PDETest.javanaming convention; likely harness-dependent misnamed tests are reported as warnings.
PDE Harness Tests
- runJUnitPluginTests — Run all plug-in tests in the PDE harness. Use for the classes listed under
PDE harness tests (*PDETest). - runJUnitPluginTestClass — Run one fully qualified
*PDETestclass. - runJUnitPluginTestClasses — Run a comma-separated set of fully qualified
*PDETestclasses in one PDE launch. Prefer it after a change touches several harness tests because Eclipse workbench startup is paid only once. The initial batch tool does not provide coverage; use the single-class or whole-project tools when coverage is required. - getActiveTarget / reloadTarget — Inspect or refresh the target platform when plug-in dependencies cannot resolve.
- Keep ordinary unit tests named
*Test.java; any test using Eclipse workspace, JDT, UI, platform, or OSGi runtime services must be named*PDETest.javaso discovery routes it to the PDE harness.
Build Tools
- runMavenBuild — Run Maven with specified goals. Provide
projectName,goals(e.g.,clean install), optionalprofiles, andtimeout. - getEffectivePom — Get the effective POM for a Maven project.
- listMavenProjects — List all Maven projects in the workspace.
- getProjectDependencies — Get Maven dependencies for a project.
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 · 69 lines · 31 tokens per session scan A e4d1dfadfb09
eclipse-test is a skill published in the GitHub repository gradusnikov/eclipse-chatgpt-plugin (166 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 977 once invoked, about $0.0002 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
aj-mcp-java8
Develop, review, debug, test, and document the AJ-MCP Java 8 SDK in this repository. Use for changes involving aj-mcp-common, aj-mcp-client, aj-mcp-server, JSON-RPC/MCP protocol models, protocol-version negotiation, STDIO, legacy HTTP/SSE, Streamable HTTP, annotation-based tools/resources/prompts, lifecycle or…
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.
run-tests
Run Embody's test suite and write new tests (Embody development).
testing-api-assertions
Verify API requests in tests. Use when testing that correct API calls are made for create, update, or delete operations. Use when testing mutations, form submissions, or actions with backend side effects.
shaft-automated-test-authoring
Use when implementing or repairing executable SHAFT Java tests for web, mobile, API, database, CLI, TestNG, JUnit, or Cucumber behavior.
shaft-recording-codegen
Use when a persisted SHAFT web, Playwright, mobile, or API recording must become compilable, repository-aware Java code or insertion blocks.