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 commands/eai-support/eai-gofer/eaigit 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/commands/eai-support/eai-gofer/eai)<a href="https://agentmods.dev/commands/eai-support/eai-gofer/eai"><img src="https://agentmods.dev/badge/commands/eai-support/eai-gofer/eai.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.00000 | $0.03953 |
| Opus 5 | $0.00000 | $0.01976 |
| Sonnet 5 | $0.00000 | $0.00791 |
| Haiku 4.5 | $0.00000 | $0.00395 |
Grade A, and why
eai 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 today.
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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eai
Use this as the single user-facing Gofer command. Apply its contract to every request after Gofer is installed. An explicit /eai, $eai, or #eai prefix is optional. Do not ask users to run numbered stage commands unless they explicitly request low-level internals.
User-Facing Contract
- Keep the command window simple: expose
eaionly. - Treat
.specify/commands/*.mdas internal stage contracts, not user-facing commands. - Keep all Gofer functions available by routing internally to the right stage contract.
- Explain progress in business language first; provide technical details when the user asks.
Controlled English Contract
Use ASD-STE100 Simplified Technical English as the target writing standard for all Gofer-authored chat, documents, commands, summaries, PR notes, error guidance, and validation artifacts. ASD-STE100 is copyright and a trademark of ASD; do not bundle the protected ASD dictionary and do not claim ASD certification.
Apply these rules before any user-facing output:
- Use short sentences. Keep instructions to 20 words or fewer where possible.
- Use one action per instruction.
- Use active voice. Use passive voice only when the actor is unknown or not important.
- Use simple present, simple past, simple future, infinitive, or imperative verb forms.
- Use approved project terms and necessary technical nouns only. Define acronyms on first use.
- Use direct words. Avoid idioms, marketing adjectives, vague praise, and hedging.
- Use vertical lists for complex information.
- Put one topic in each paragraph.
- For errors, write: what happened, why it matters, what to do next, and the exact safe command when one exists.
- Keep raw logs, stack traces, IDs, and secrets out of chat unless the user asks for technical detail.
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.
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.
- today Changed · +6 lines 09e2686e3212
- 5d ago First seen · 221 lines · 0 tokens per session scan A bd055284f0c1
eai is a command published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,953 tokens. 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 commands, from other repositories
spec-kitty-standalone
This host should read Spec Kitty's canonical standalone-invocation skill pack at.
spec-kitty.tasks-outline
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
spec-kitty.tasks-packages
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
spec-kitty.analyze
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
spec-kitty.charter
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
spec-kitty.research
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.