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/andreagriffiths11/teamxray/copilot-instructionsgit clone --depth 1 https://github.com/AndreaGriffiths11/teamxrayWrote 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/instructions/andreagriffiths11/teamxray/copilot-instructions)<a href="https://agentmods.dev/instructions/andreagriffiths11/teamxray/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/andreagriffiths11/teamxray/copilot-instructions.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 | $0.01416 | $0.01416 |
| Opus 5 | $0.00708 | $0.00708 |
| Sonnet 5 | $0.00283 | $0.00283 |
| Haiku 4.5 | $0.00142 | $0.00142 |
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 5d 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 — 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
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.
- 5d ago First seen · 112 lines · 1,416 tokens per session scan A f53bfbab1ac4
teamxray copilot-instructions.md is an instructions file published in the GitHub repository AndreaGriffiths11/teamxray (17 stars, last pushed today), licensed MIT. It adds 1,416 tokens to every session, about $0.0071 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
github-mcp-server copilot-instructions.md
Copilot instructions for github/github-mcp-server, covering github mcp server - copilot instructions, project overview, critical build & validation steps, required commands (run before committing) and when modifying mcp tools/endpoints.
vscode-gitlens AGENTS.md
AGENTS.md instructions for gitkraken/vscode-gitlens, covering gitlens development guide, working style expectations, development environment, development commands and git & repository guidelines.
mcp-server-azure-devops AGENTS.md
Instructions for Tiberriver256/mcp-server-azure-devops: /home/tiberriver256/repos/mcp-server-azure-devops/docs/important-knowledge/azure-devops-rest-api-research.md Researching Azure DevOps REST APIs, selecting api-version, or handling Azure DevOps Server (on-prem) endpoints.
ebay-mcp AGENTS.md
Instructions for YosefHayim/ebay-mcp, covering agents.md, what this is, instruction sources, validation commands and module map (src/).
vscode-gitlens CLAUDE.md
Claude Code instructions for gitkraken/vscode-gitlens, a project described as: Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via…
link CLAUDE.md
Claude Code instructions for lanes-sh/link, covering working in this repository, work on a branch, in a worktree, never run lanes link from a worktree without laneslinkhome, anything touching a real account is the operator's call and a release publishes, and npm does not give a version back.