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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/eai-support/eai-gofer/agents-md"><img src="https://agentmods.dev/badge/instructions/eai-support/eai-gofer/agents-md/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/agents-md"><img src="https://agentmods.dev/badge/instructions/eai-support/eai-gofer/agents-md.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.01381 | $0.01381 |
| Opus 5.5 | $0.00552 | $0.00552 |
| Sonnet 5.5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
eai-gofer AGENTS.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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project: gofer | Language: Unknown | Package Manager: Not detected
User-Facing Response Gate
Before each user-facing reply, check the draft against these rules:
- Lead with the business outcome, effect, risk, or decision.
- Use concise, simple language.
- Include technical detail only when it supports a decision or the user asks for it.
- If any check fails, rewrite the reply before sending it.
Always-On EAI Contract
Apply this contract to every request after Gofer is installed for this repo or
AI coding app. The user does not need to type /eai or $eai.
- Preserve the user's request. Do not rewrite it or add a visible command prefix.
- Treat an explicit
/eai(Claude, Copilot, Antigravity, Grok, or VS Code) or$eai(Codex) prefix as an idempotent request for the same contract. - Apply Gofer's Controlled English and business-first response rules.
- Select the internal pipeline stage. Do not make the user select a stage.
- Check workspace health before meaningful repo work, tool use, or a pipeline stage. Do not repeat setup on every message.
- When the user explicitly asks to update Gofer, use its maintenance contract only.
Core Pipeline Stages
0_gofer_start
Define the business problem and scenario for Gofer to analyse and solve.
1_gofer_research
Research codebase, CLI integrations, and technology landscape for the target feature.
2_gofer_specify
Generate a feature specification from research findings and approved proposal review.
3_gofer_plan
Create a detailed technical implementation plan with architecture, data model, and contracts.
4_gofer_tasks
Break down the implementation plan into dependency-ordered, parallelisable tasks.
5_gofer_implement
Execute all tasks from tasks.md phase by phase with feedback loops and engineering review.
6_gofer_validate
Validate implemented work with evidence-backed scoring, blast-radius analysis, and engineering review.
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 5af1b61dcd18
- 1mo ago Changed · +1 lines · +30 tokens per session b792f9a751d4
- 1mo ago Changed · +19 lines · +193 tokens per session efda46c6a59f
- 1mo ago First seen · 180 lines · 1,022 tokens per session scan A 0c9d1a0a7450
eai-gofer AGENTS.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 1,381 tokens to every session, about $0.0055 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-09-03.
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.