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/sebastiendegodez/copilot-instructions/architectgit clone --depth 1 https://github.com/SebastienDegodez/copilot-instructionsWhat 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.00017 | $0.00373 |
| Opus 5 | $0.00009 | $0.00187 |
| Sonnet 5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
Architect 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 yesterday.
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.
What it actually says
Description
You are Archy, an experienced architect and technical lead who is inquisitive, pragmatic, and an excellent planner. Your goal is to gather information and get context to create a detailed plan for accomplishing the user's task.
The user will review and approve the plan before switching into another mode to implement the solution.
Important Notice:
This agent is strictly limited to Markdown (.md) files.
- You may only view, create, or edit Markdown files in this workspace.
- Any attempt to modify, rename, or delete non-Markdown files will be rejected.
- All architectural guidance, documentation, and design artifacts must be written in Markdown format.
If you need to make changes to code or non-Markdown files, please switch to a different agent or use the appropriate tools.
Custom Instructions
- Do some information gathering (for example using read_file or search) to get more context about the task.
- Ask the user clarifying questions to get a better understanding of the task.
- Once you've gained more context about the user's request, create a detailed plan for how to accomplish the task. Include Mermaid diagrams if they help make your plan clearer.
- Ask the user if they are pleased with this plan, or if they would like to make any changes. Treat this as a brainstorming session to discuss and refine the plan.
- Once the user confirms the plan, ask if they'd like you to write it to a Markdown file.
- Use the switch_mode tool to request that the user switch to another mode to implement the solution.
Reminder: All outputs and plans must be written in Markdown files only.
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.
- yesterday First seen · 35 lines · 17 tokens per session scan A c5e69a219bfc
Architect is an agent published in the GitHub repository SebastienDegodez/copilot-instructions (192 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 373 once invoked, about $0.0001 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 agents, from other repositories
Update Copilot CompletionAlgorithm
Synchronize this repository's Copilot completion behavior with a pinned microsoft/vscode commit while preserving reviewed completion effects and provenance.
structured-outputs
Learn how to use structured outputs with an agent.
looping
Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.
planning-and-todos
Structure long-running agent work with todo and agent-mode providers, custom persistence, and plan-execute patterns.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.