endgame

A skill for preparing end-of-milestone test plans from a GitHub milestone issue. A milestone groups related work that should be checked before a release.

In plain words
What is it for?
Use it to fetch one endgame issue, find the tasks assigned to a developer, and create a separate test plan for each linked task or pull request.
Why use it?
It divides the issue's assigned tasks among research workers and keeps each resulting test plan in the project's expected folder.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/microsoft/copilot-for-eclipse/endgame
Any agent
npx skills add microsoft/copilot-for-eclipse --skill endgame
Clone the repo
git clone --depth 1 https://github.com/microsoft/copilot-for-eclipse

Made for: Claude Code, Codex.

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,364 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00071 $0.01364
Opus 5 $0.00036 $0.00682
Sonnet 5 $0.00014 $0.00273
Haiku 4.5 $0.00007 $0.00136

Measured 2d ago against content hash 25caaf1f9c3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.github/skills/endgame/SKILL.md · 174 lines

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:

  1. Do NOT run gh pr view or gh issue view for individual tasks — only run it once for the main endgame issue.
  2. Do NOT research or analyse any task yourself.
  3. Do NOT create any test-plan files yourself.
  4. IMMEDIATELY call runSubagent for 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.

Read the full file on GitHub · 174 lines

Changes

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.

  1. 2d ago First seen · 174 lines · 71 tokens per session scan A 25caaf1f9c3f

Subscribe to this mod's changes

endgame is a skill published in the GitHub repository microsoft/copilot-for-eclipse (122 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 1,364 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens