Borrowing it
Nothing to install: this file belongs to eai-support/eai-gofer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eai-support/eai-gofer/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/eai-support/eai-goferWrote 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/eai-support/eai-gofer/copilot-instructions)<a href="https://agentmods.dev/instructions/eai-support/eai-gofer/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/eai-support/eai-gofer/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.
<a href="https://agentmods.dev/instructions/eai-support/eai-gofer/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/eai-support/eai-gofer/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00756 | $0.00756 |
| Opus 5.5 | $0.00302 | $0.00302 |
| Sonnet 5.5 | $0.00151 | $0.00151 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
eai-gofer 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Always-On EAI Contract
Apply Gofer to every request. Preserve the user prompt and do not add a visible command prefix. Route internally and select the next stage. Check workspace health only before meaningful repo work. Use the update path only for explicit Gofer maintenance requests.
Issue and pull request titles
Say what changes, who or what benefits, and the outcome or risk it addresses.
Keep titles concise and in business language. Use a prefix such as CURATE: only when it helps identify a programme. The prefix should not replace the outcome.
An issue describes the outcome needed:
Prevent [risk] for [user or system] by [needed capability]
Example from Issues2025 #3375: Prevent broken EAI app data links caused by inconsistent Object Type slugs.
A pull request describes the change delivered and the outcome it enables:
Enable [outcome] for [user or system] by [change made]
Project Overview
gofer is a Unknown project.
Gofer Pipeline
This project uses Gofer for spec-driven development. #eai is optional. Use the
same core pipeline for every request: Gofer Start -> research -> specify -> plan
-> tasks -> implement -> validate.
Gofer routes internally through .specify/commands/*.md contracts, so numbered
stage prompts stay hidden unless explicitly needed for internals. Before EAI
readiness, classify the request: app delivery continues directly, while clear
non-app work asks once before skipping EAI tenant/app setup. Validation is the
terminal quality gate and includes the final engineering review loop. Artifacts
live in .specify/specs/{feature}/.
Token And Cost Policy
- Treat
.specify/memory/gofer-model-policy.yamlas advisory policy. Choose the lowest-cost model qualified by a fresh signed host receipt and independent benchmark evidence. Do not select a model from a static name or price. - Prefer compact Copilot prompts and built-in workspace context. Escalate only when a cheaper qualified pass fails or the task needs stronger review.
- Keep raw command and search output out of chat context. Save durable summaries
to
.specify/specs/{feature}/context-bundle.mdand continue from artifacts. - Reuse stable non-secret prefixes for provider caching where supported: Gofer scaffold, AGENTS/Copilot instructions, constitution, repo map, stage contracts, and validation rubric.
- After large research, planning, implementation, or validation bursts, checkpoint artifacts and compact/clear/resume context when the host supports 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.
- 9d ago Changed · +16 lines · +136 tokens per session 89f5bf79673c
- 1mo ago Changed · -2 lines · -12 tokens per session 8406dbffe831
- 1mo ago Changed · +11 lines · +75 tokens per session 791da0a8b863
- 1mo ago First seen · 63 lines · 557 tokens per session scan A ea6d48e0e971
eai-gofer copilot-instructions.md is an instructions file published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 756 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.