Borrowing it
Nothing to install: this file belongs to gradusnikov/eclipse-chatgpt-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gradusnikov/eclipse-chatgpt-plugin/main/.claude/skills/eclipse-analyze/SKILL.mdgit 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-analyze)<a href="https://agentmods.dev/skills/gradusnikov/eclipse-chatgpt-plugin/eclipse-analyze"><img src="https://agentmods.dev/badge/skills/gradusnikov/eclipse-chatgpt-plugin/eclipse-analyze/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gradusnikov/eclipse-chatgpt-plugin/eclipse-analyze"><img src="https://agentmods.dev/badge/skills/gradusnikov/eclipse-chatgpt-plugin/eclipse-analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.01575 |
| Opus 5.5 | $0.00017 | $0.00630 |
| Sonnet 5.5 | $0.00009 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
eclipse-analyze 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eclipse Code Analysis
Analyze Java code using Eclipse's JDT (Java Development Tools) infrastructure. These tools provide accurate, compiler-level analysis — not text-based guessing.
Reading Code Efficiently
These tools are designed to minimize context window usage. Follow the outline-first pattern:
-
getClassOutline — Start here. Returns class declaration, field declarations, method signatures (no bodies), and inner types — all with line numbers and the first sentence of each member's Javadoc (an undocumented override reports its supertype's text, flagged
javadocInherited). A 500-line class becomes ~30 lines. ProvidefullyQualifiedClassName. SetincludeFields=falseto omit fields;javadoc=FULLrenders whole comments,javadoc=NONEleaves them out. -
getMethodSource — After seeing the outline, read only the methods you need. Accepts comma-separated
methodNames(e.g.,"save,findById,delete"). Returns source with line numbers. SetincludeJavadoc=falseto skip doc comments. UsemethodSignatureto disambiguate overloads (e.g.,"String"matches methods with a String parameter). -
getFilteredSource — Middle ground: returns the full source but collapses methods you don't need to their signatures. Provide
methodNamesto expand specific methods; all others are shown as one-line signatures with line ranges. SetexcludeImports=true(the default) to collapse the import block. Line numbers always match the original file for accurate editing. -
getSource — Full source dump. Use only for small classes or when you need everything. Prefer the tools above to save context.
-
readProjectResource — Read any file by path. Supports
startLine/endLinefor ranges,showLineNumbers=truefor editing, andexcludeImports=trueto collapse Java import blocks.
Choosing the Right Tool
| Scenario | Tool | Why |
|---|---|---|
| Understand class structure | getClassOutline |
Signatures only, ~90% smaller |
| Read 1-3 specific methods | getMethodSource |
Surgical reads with line numbers |
| Read class but focus on 2 methods | getFilteredSource |
Full context, collapsed noise |
| Small class (<100 lines) | getSource |
Overhead not worth optimizing |
| Referenced-library class | getSource |
Uses attached source or decompiles the class |
| Diagnose which JAR/root won | explainTypeResolution |
Shows the project-specific JDT classpath decision |
| Compare a historical file | gitReadFile |
Reads a revision or staged index without checkout |
| Non-Java file or specific line range | readProjectResource |
Works with any file type |
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.
- 1mo ago Changed f76669939f46
- 2mo ago First seen · 80 lines · 43 tokens per session scan A b232f493e66f
eclipse-analyze is a skill published in the GitHub repository gradusnikov/eclipse-chatgpt-plugin (175 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 1,575 once invoked, about $0.0002 per session on Opus 5.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
mcp-java-dev-tools-bug-drill
Discover bounded Java method drill candidates or run a Probe-guided diagnostic drill for one selected method and return an evidence-backed Markdown report.
mcp-java-dev-tools-bug-fix
Create a proposal-only, evidence-backed Java bug-fix diagnosis from issue context and behavioral reproduction steps. Use when expected behavior and how to reproduce are known, even when endpoint, class, method, logs, or technical request details are not yet known.
mcp-java-dev-tools-line-probe-run
Run strict single-line JVM probe verification. Use for line-hit checks, route validation, and fail-closed probe execution.
mcp-java-dev-tools-performance-suite
Run MCP-first Java performance suites with required strict line-hit verification, concurrency-based workload contracts, and deterministic threshold evaluation. Use when executing or reviewing performance-suite Artifacts under .mcpjvm/.../plans/performance or execution profiles with suiteType=performance.
mcp-java-dev-tools-failure-lens
Investigate a pasted Java stack trace against an attached Sidecar Agent using bounded guided or hands-off reproduction. Use when a user wants to reproduce a Java exception with runtime Probe evidence; never use for static-only diagnosis, CI/regression execution, generic replay, or automatic Bug Fix handoff.
mcp-java-dev-tools-performance-plan-crafter
Create or update deterministic performance plans (metadata.json, contract.json, plan.md) under .mcpjvm/.../plans/performance. Use when authoring workload-centric Java performance-suite Artifacts with required strict line-hit verification.