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.
git 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/commands/microsoft/copilot-for-eclipse/resolve-single-comment)<a href="https://agentmods.dev/commands/microsoft/copilot-for-eclipse/resolve-single-comment"><img src="https://agentmods.dev/badge/commands/microsoft/copilot-for-eclipse/resolve-single-comment.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.1 | $0.00009 | $0.01424 |
| Opus 5 | $0.00005 | $0.00712 |
| Sonnet 5 | $0.00002 | $0.00285 |
| Haiku 4.5 | $0.00001 | $0.00142 |
Grade A, and why
resolve-single-comment 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Single PR Comment Resolution
When to Apply
Apply this instruction when resolving an individual PR review comment. This is typically invoked as part of the broader PR comment resolution workflow.
Critical Rules
⚠️ THIS IS A BLOCKING WORKFLOW: Each step must complete before proceeding to the next.
CONFIRMATION STEPS ARE MANDATORY: Steps 4 and 8 require explicit user approval. You MUST stop and wait for user input.
DO NOT PROCEED WITHOUT CONFIRMATION: If the user has not responded, DO NOT continue to the next step.
Input
pr_number: The PR numbercomment_id: The comment ID from the comments.json file
Read the comment details from .github/pullrequests/{pr_number}/comments.json using the comment_id:
id: The comment ID (for replying)path: The file path where the comment was madeline: The line number in the filebody: The review comment content
Resolution Steps
1. Understand the Context
- Read the file at the specified
lineand surrounding context (±10-20 lines) - Parse the comment
bodyto understand what the reviewer is requesting - If more context is needed, read additional lines from the file
2. Classify the Comment Type
Determine the type of feedback:
- Code style: Formatting, naming conventions, import organization
- Bug fix: Logic error, null check, edge case handling
- Refactoring: Extract method, simplify logic, reduce duplication
- Documentation: Add/update Javadoc, comments, or explanations
- Best practice: Thread safety, resource management, error handling
- Question/Clarification: Reviewer needs explanation (may not require code change)
3. Propose the Fix
- Identify the specific change needed
- Present the proposed change to the user with:
- What will be changed
- Why this addresses the reviewer's feedback
- Any related changes needed (e.g., updating callers)
4. Get User Confirmation ⛔ BLOCKING STEP
⛔ STOP HERE AND WAIT FOR USER RESPONSE
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.
- yesterday First seen · 161 lines · 9 tokens per session scan A f34698e15a39
resolve-single-comment is a command published in the GitHub repository microsoft/copilot-for-eclipse (122 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 1,424 once invoked, about $0.0000 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-09-07.
Other commands, from other repositories
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.