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 instructions/microsoft/copilot-for-eclipse/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/copilot-for-eclipseWhat 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.05576 | $0.05576 |
| Opus 5 | $0.02788 | $0.02788 |
| Sonnet 5 | $0.01115 | $0.01115 |
| Haiku 4.5 | $0.00558 | $0.00558 |
Grade A, and why
copilot-for-eclipse copilot-instructions.md 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 2d 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 — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot for Eclipse - Copilot Instructions
Project Overview
This is the GitHub Copilot for Eclipse plugin - an Eclipse IDE extension that brings AI-powered code completions, chat assistance, and intelligent coding features to Eclipse users.
Key Features
- Code Completions: Real-time AI-powered code suggestions using ghost text and inline completions
- Chat Interface: Conversational AI assistance with agent mode, custom chat modes, and context-aware responses
- Agent Tools: Multi-step autonomous coding with tools for file operations, error analysis, and terminal execution
- Language Server Integration: LSP4E-based connection to GitHub Copilot language server
- Authentication: GitHub OAuth integration for Copilot subscription management
- Multi-Platform Support: Windows, macOS (x64/aarch64), and Linux (x64/aarch64)
Tech Stack
- Java: Primary language (Java 17+, with Eclipse 4.31+ requiring Java 21+)
- Eclipse RCP/OSGi: Plugin architecture using Eclipse platform APIs
- Maven/Tycho: Build system for Eclipse plugin development
- LSP4E: Language Server Protocol integration for Eclipse
- Node.js/JavaScript: Copilot language server (agent binaries bundled per platform)
- JDT: Java Development Tools integration for Java-specific features
- SWT: Standard Widget Toolkit for UI components
Validating Changes
You MUST verify compilation and code quality before declaring work complete!
-
ALWAYS run Maven build to check for compilation errors:
.\mvnw clean verify -
CHECK Checkstyle compliance (Google Java Style with custom rules):
.\mvnw checkstyle:check -
RUN tests before submitting changes:
.\mvnw test -
FIX all compilation errors, Checkstyle violations, and test failures before moving forward
Maven Build Structure
- Root POM coordinates multi-module build with Tycho
- Each bundle/feature/test has its own POM inheriting from root
- Checkstyle validation runs during
verifyphase - Target platform defined in
base.target,target-terminal.target,target-tm-terminal.target
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.
- 2d ago First seen · 588 lines · 5,576 tokens per session scan A 61cbebc9b641
copilot-for-eclipse copilot-instructions.md is an instructions file published in the GitHub repository microsoft/copilot-for-eclipse (122 stars, last pushed 6d ago), licensed MIT. It adds 5,576 tokens to every session, about $0.0279 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.