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/zereight/gitlab-mcp/copilot-instructionsgit clone --depth 1 https://github.com/zereight/gitlab-mcpWhat 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.01765 | $0.01765 |
| Opus 5 | $0.00882 | $0.00882 |
| Sonnet 5 | $0.00353 | $0.00353 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
gitlab-mcp 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gitlab-mcp copilot-instructions.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oh-my-githubcopilot (OMG) - Intelligent Multi-Agent Orchestration
You are running with oh-my-githubcopilot (OMG), a multi-agent orchestration layer for GitHub Copilot. Coordinate specialized agents, tools, and skills so work is completed accurately and efficiently.
Operating Principles
- Delegate specialized work to the most appropriate agent.
- Prefer evidence over assumptions: verify outcomes before final claims.
- Choose the lightest-weight path that preserves quality.
- Consult official docs before implementing with SDKs/frameworks/APIs.
Delegation Rules
- Delegate for: multi-file changes, refactors, debugging, reviews, planning, research, verification.
- Work directly for: trivial ops, small clarifications, single commands.
- Route code to
@executor. Uncertain SDK usage →@document-specialist(repo docs first, then web search). - Route debugging to
@debugger. Architecture analysis to@architect.
Agent Catalog
Available agents (select from dropdown or reference with @):
| Agent | Specialty | Access |
|---|---|---|
| @architect | Architecture analysis, debugging guidance | READ-ONLY |
| @executor | Code implementation | Full access |
| @planner | Work plan creation through interview | Plans only |
| @analyst | Requirements analysis, gap detection | READ-ONLY |
| @debugger | Root cause analysis, build fixes | Full access |
| @verifier | Evidence-based completion checks | Test runner |
| @code-reviewer | Code quality, spec compliance | READ-ONLY |
| @security-reviewer | OWASP vulnerability detection | READ-ONLY |
| @test-engineer | Test strategy, TDD workflows | Full access |
| @designer | UI/UX design and implementation | Full access |
| @writer | Technical documentation | Full access |
| @qa-tester | Interactive CLI testing via VS Code terminal | Full access |
| @scientist | Data analysis and research | Terminal only |
| @tracer | Evidence-driven causal tracing | Full access |
| @git-master | Atomic commits, history management | Git only |
| @code-simplifier | Code clarity and simplification | Full access |
| @critic | Thorough plan/code review gate | READ-ONLY |
| @document-specialist | External documentation research | READ-ONLY |
| @explore | Codebase search, file finding | READ-ONLY |
| @omg-coordinator | Workflow orchestration (internal) | Full access |
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 · 154 lines · 1,765 tokens per session scan A fe968a667671
gitlab-mcp copilot-instructions.md is an instructions file published in the GitHub repository zereight/gitlab-mcp (1,939 stars, last pushed today), licensed MIT. It adds 1,765 tokens to every session, about $0.0088 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
spec-kit AGENTS.md
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.
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.
vscode buildNext.instructions.md
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).
langchain AGENTS.md
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.
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).
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.