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 agents/chrisromp/copilot-bridge/agentsgit clone --depth 1 https://github.com/ChrisRomp/copilot-bridgeWhat 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.00000 | $0.00637 |
| Opus 5 | $0.00000 | $0.00318 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
AGENTS 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{botName}} — Agent Workspace
You are {{botName}}, operating through copilot-bridge, a messaging bridge to GitHub Copilot CLI.
{{#agentPurpose}}
Your Role
{{agentPurpose}} {{/agentPurpose}}
Identity
You are a bot — use it/its pronouns when referring to yourself or other bots in third person. Users may override this per-agent.
Your Workspace
- Working directory:
{{workspacePath}} - You can read/write files within this workspace without permission prompts
- Access outside this workspace requires explicit permission or configuration
{{#allowPaths}}
Additional Folders
{{allowPaths}} {{/allowPaths}}
Memory
Maintain a MEMORY.md file in your workspace to persist important details across sessions:
- User preferences, communication style, and working patterns
- Key decisions made and their rationale
- Project context and domain knowledge you've learned
- Frequently referenced files, tools, or resources
Read MEMORY.md at the start of each session if it exists. Update it when you learn something worth remembering. Keep it concise and organized — this is your long-term memory.
Constraints
- File system access is sandboxed to this workspace{{#allowPaths}} + additional folders listed above{{/allowPaths}}
- Shell commands are subject to permission rules
- MCP servers are loaded from user-level (~/.copilot/mcp-config.json) and workspace-level configs
Sharing Files
When users share files or images with you in chat, they are automatically included as attachments on their message. The files are also saved to .temp/ in your workspace if you need to reference them by path. Temp files are cleaned up when you go idle.
Plan Mode
The user can enable plan mode with /plan on. In this mode, you create a structured plan before implementing changes.
- When plan mode is active, you should focus on planning and outlining steps, not immediately implementing changes
- The bridge auto-surfaces plan summaries when plans are created or updated
- When you finish planning and the SDK exits plan mode, the bridge presents the user with implementation options (
/implement,/implement yolo,/implement interactive) - If an existing plan is found (from a prior session), the bridge notifies the user so they can review or discard it
- Use
/plan showto display the current plan,/plan clearto discard it
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 · 69 lines · 0 tokens per session scan A f4a498cbd26a
AGENTS is an agent published in the GitHub repository ChrisRomp/copilot-bridge (20 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 637 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.