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/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/eai-support/eai-gofer/claude-md"><img src="https://agentmods.dev/badge/instructions/eai-support/eai-gofer/claude-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/claude-md"><img src="https://agentmods.dev/badge/instructions/eai-support/eai-gofer/claude-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.00888 | $0.00888 |
| Opus 5.5 | $0.00355 | $0.00355 |
| Sonnet 5.5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
eai-gofer CLAUDE.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 13d 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.
This is a copy
92% identical to OpenAIWorkshop copilot-instructions.md — 154 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
See @AGENTS.md for project conventions, commands, and code style.
Always-On EAI Contract
Gofer applies to every request. Preserve the user prompt. Do not add a visible command prefix. Select the internal route and 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]
Workflow Orchestration
1. Plan Node Default
- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
- If something goes sideways, STOP and re-plan immediately – don't keep pushing
- Use plan mode for verification steps, not just building
- Write detailed specs upfront to reduce ambiguity
2. Subagent Strategy
- Use subagents liberally to keep main context window clean
- Offload research, exploration, and parallel analysis to subagents
- For complex problems, throw more compute at it via subagents
- One task per subagent for focused execution
3. Self-Improvement Loop
- After ANY correction from the user: update
tasks/lessons.mdwith the pattern - Write rules for yourself that prevent the same mistake
- Ruthlessly iterate on these lessons until mistake rate drops
- Review lessons at session start for relevant project
4. Verification Before Done
- Never mark a task complete without proving it works
- Diff behavior between main and your changes when relevant
- Ask yourself: "Would a staff engineer approve this?"
- Run tests, check logs, demonstrate correctness
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.
- 13d ago Changed · +16 lines · +136 tokens per session 9d23163b2f1a
- 1mo ago Changed · +12 lines · +85 tokens per session 56f269619f20
- 1mo ago First seen · 76 lines · 667 tokens per session scan A 96a9e003a5fd
eai-gofer CLAUDE.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 888 tokens to every session, about $0.0036 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to OpenAIWorkshop copilot-instructions.md, differing in 154 lines, and is treated as a copy.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.