What is teamxray copilot-instructions.md?

Repository-specific instructions for developing the Team X-Ray VS Code extension, which analyzes Git and GitHub data with AI to show collaboration patterns.

Use them when modifying the extension so the agent follows its coding conventions and runs the relevant checks.

They give an agent the project's expected response style and the commands used to build, test, lint, and validate changes.

How AndreaGriffiths11/teamxray configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to AndreaGriffiths11/teamxray. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AndreaGriffiths11/teamxray/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/AndreaGriffiths11/teamxray

Made for: GitHub Copilot.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/andreagriffiths11/teamxray/copilot-instructions/github.svg)](https://agentmods.dev/instructions/andreagriffiths11/teamxray/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/andreagriffiths11/teamxray/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/andreagriffiths11/teamxray/copilot-instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/andreagriffiths11/teamxray/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/andreagriffiths11/teamxray/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,416 This file is loaded in full into every session.

When invoked 1,416 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01416	$0.01416
Opus 5.5	$0.00566	$0.00566
Sonnet 5.5	$0.00283	$0.00283
Haiku 4.5	$0.00142	$0.00142

Measured 2mo ago against content hash f53bfbab1ac4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.github/copilot-instructions.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Copilot Instructions for MCP Team X-Ray Extension

Repository: AndreaGriffiths11/teamxray

A VS Code extension that reveals the humans behind a codebase — their communication styles, hidden strengths, and collaboration patterns — by analyzing Git/GitHub data through AI.

Response Style

Code only, no explanation unless asked.
Bullets over paragraphs. No preamble.
One file per response when possible — avoid showing entire modules unless specifically requested.
Link to docs instead of quoting them — assume the user can read.

Build, Test, and Lint Commands

npm run compile          # Webpack build (development)
npm run package          # Production build with source maps
npm run watch            # Watch mode for development
npm run lint             # ESLint
npm run test             # VS Code extension tests (via @vscode/test-cli)
npm run compile-tests    # Compile test files only (tsc)
npm run eval:run         # Run evalite evaluations

Validating Extension Changes

Compilation success does NOT mean the extension works. This is a VS Code extension — runtime errors (activation failures, missing modules, ESM/CJS conflicts) only surface when the extension loads in VS Code. The full validation loop is:

npm run compile — fix any webpack errors
Reload the VS Code extension host (Cmd+Shift+P → "Developer: Reload Window")
Check the "Team X-Ray" output channel for activation errors
If the extension fails at runtime, the webpack build was not sufficient — investigate the runtime error

Never declare a runtime issue fixed based solely on webpack compilation. After making changes, tell the user to reload VS Code and wait for their confirmation before considering the issue resolved. Do not say "✅ Compiled successfully" as if it means the fix worked — it only means webpack produced a bundle.

Architecture

Data Flow: Repository → local Git analysis → Copilot SDK (default) → GitHub Models API (fallback or direct setting) → Human Insights

Read the full file on GitHub · 112 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.

2mo ago First seen · 112 lines · 1,416 tokens per session scan A f53bfbab1ac4

Subscribe to this mod's changes

teamxray copilot-instructions.md is an instructions file published in the GitHub repository AndreaGriffiths11/teamxray (19 stars, last pushed 3d ago), licensed MIT. It adds 1,416 tokens to every session, about $0.0057 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.

azure-devops chatgpt github github-models mcp-server vscode

teamxray copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
teamxray copilot-instructions.mdAndreaGriffiths11/teamxray	Instructions file	19	3d ago	MIT	A	1,416	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

teamxray: Instructions file for GitHub Copilot