GitHub Copilot for Eclipse is an Eclipse IDE plugin that adds AI-assisted code completion, edit suggestions, conversational agent support, and connections to external tools through MCP. Eclipse developers use it for coding assistance and more autonomous, project-aware development tasks. The catalogue entries provide skills and instructions for working with Copilot in Eclipse.
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 skills add microsoft/copilot-for-eclipse --skill endgamegit clone --depth 1 https://github.com/microsoft/copilot-for-eclipseWrote 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/microsoft/copilot-for-eclipse/endgame)<a href="https://agentmods.dev/skills/microsoft/copilot-for-eclipse/endgame"><img src="https://agentmods.dev/badge/skills/microsoft/copilot-for-eclipse/endgame/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/microsoft/copilot-for-eclipse/endgame"><img src="https://agentmods.dev/badge/skills/microsoft/copilot-for-eclipse/endgame.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.00071 | $0.01364 |
| Opus 5.5 | $0.00028 | $0.00546 |
| Sonnet 5.5 | $0.00014 | $0.00273 |
| Haiku 4.5 | $0.00007 | $0.00136 |
Grade A, and why
endgame 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 2mo 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Endgame Verification Skill
Use this skill to run an endgame verification pass for a GitHub milestone issue.
Each task in the issue is delegated to a subagent that researches the linked
PR/issue and writes a test plan under com.microsoft.copilot.eclipse.swtbot.test/test-plans/.
Workflow
⚠️ CRITICAL — YOU MUST FOLLOW THESE RULES:
- Do NOT run
gh pr vieworgh issue viewfor individual tasks — only run it once for the main endgame issue. - Do NOT research or analyse any task yourself.
- Do NOT create any test-plan files yourself.
- IMMEDIATELY call
runSubagentfor each task after parsing the issue — no delays, no research.
Step 1 — Ask the user for inputs
Ask for:
- The GitHub endgame issue URL
(e.g.
https://github.com/microsoft/copilot-for-eclipse/issues/XXXX) - The user's GitHub account name
Step 2 — Fetch the endgame issue (ONE call only)
gh issue view <issue_number> --repo microsoft/copilot-for-eclipse --json body --jq '.body'
Parse the body to find all tasks (checkboxes) assigned to the specified user. Extract each task's title and any linked PR/issue URL as plain text.
STOP — do NOT fetch any of the linked PRs or issues.
Step 3 — Process each task via subagent
For each task, call runSubagent with:
- description:
"Endgame: <short_task_title>" - prompt: the template below, filled in with only the info you extracted.
Subagent prompt template
Task Details
- Task Number: <N>
- Task Title: <task_title>
- Assignee: <username>
- Related Issue/PR: <link_if_available> (NOT YET FETCHED — you must fetch this)
Your Mission
YOU (the subagent) must research this task AND create the test-plan file.
Step 1: Research the task
- Fetch the linked PR or issue with
gh pr view/gh issue view. - Understand what feature or fix needs to be verified.
- If anything is ambiguous or unclear after reading the PR/issue, ask the user for clarification before proceeding. Keep asking until you have enough information to write concrete, accurate test steps.
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.
- 2mo ago First seen · 174 lines · 71 tokens per session scan A 25caaf1f9c3f
endgame is a skill published in the GitHub repository microsoft/copilot-for-eclipse (129 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 1,364 once invoked, about $0.0003 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.