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 instructions/eai-support/eai-gofer/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.svg" alt="Measured on agentmods" 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 | $0.01022 | $0.01022 |
| Opus 5 | $0.00511 | $0.00511 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 180 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.
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.
Optional Helper Commands
0a_problem_validation
Validate the business problem using 5 Whys root-cause analysis and stakeholder mapping when the kickoff needs deeper framing.
7_gofer_save
Save session state and create a handoff checkpoint for resumption in a new context.
8_gofer_branding
Brand Gofer templates and stakeholder documents for a company or consulting-firm look and feel.
9_gofer_tests
Generate comprehensive test suites from four testing perspectives for a target component.
10_gofer_cloud
Deploy and configure the Gofer cloud integration for remote pipeline execution.
7a_stakeholder_comms
Generate stakeholder-facing communications after validation as an optional follow-up, not a core pipeline stage.
gofer_constitution
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 · 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 yesterday), licensed Apache-2.0. It adds 1,022 tokens to every session, about $0.0051 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-09-03.
Other instructions, from other repositories
agent-levers AGENTS.md
Instructions for fmind/agent-levers, covering agents.md, conventions, workflow and layout.
agent-evolutions AGENTS.md
AGENTS.md instructions for fmind/agent-evolutions, covering agents.md, conventions, workflow and layout.
agent-levers CLAUDE.md
Instructions for fmind/agent-levers, a project described as: Levers for AI coding agents (Claude Code, Gemini CLI, GitHub Copilot, OpenCode) — multiply the agent's force, divide the human's effort.
agent-levers GEMINI.md
Instructions for fmind/agent-levers, a project described as: Levers for AI coding agents (Claude Code, Gemini CLI, GitHub Copilot, OpenCode) — multiply the agent's force, divide the human's effort.
agent-evolutions CLAUDE.md
Claude Code instructions for fmind/agent-evolutions, a project described as: Genetic exploration of solution spaces for AI coding agents (Claude Code, Gemini CLI, GitHub Copilot, OpenCode) — gather a verifiable objective, evolve variants, apply the winner.
agent-evolutions GEMINI.md
Gemini CLI instructions for fmind/agent-evolutions, a project described as: Genetic exploration of solution spaces for AI coding agents (Claude Code, Gemini CLI, GitHub Copilot, OpenCode) — gather a verifiable objective, evolve variants, apply the winner.