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/antfu/ghfs/agents-mdgit clone --depth 1 https://github.com/antfu/ghfsWhat 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.02139 | $0.02139 |
| Opus 5 | $0.01069 | $0.01069 |
| Sonnet 5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
ghfs 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules
- CLI related logics, usage of
@clack/prompts,console.logcan only be undersrc/cli/ - GitHub related logics, usage of
octokitcan only be undersrc/providers/github/ - Pure/simple functions should better be under
src/utils/and be tested alongside. - Avoid duplicating logics, refactor them to reuse.
- Always use
patheinstead ofnode:path - At this moment, we don't care about breaking changes at all, don't worry about migration or backward compatibility.
Keyboard accessibility (UI)
- Every interactive element under
ui/must be operable without a mouse. When adding a button, tab, pill, or dialog action, pair it with either (a) nativeTab+Enter/Space— the default focus ring must be visible — or (b) a command registered inui/composables/useAppCommands.ts, and render<Kbd command="..." />next to it so the binding is discoverable. - Text inputs & textareas get a single-key focus shortcut (e.g.
/for search,nfor comment).Escapealready blurs focused inputs globally viaui/composables/useCommandHandler.ts— do not re-implement it. Tag the element withdata-shortcut="<id>"so the command'srun()canquerySelectorit. - Submit-from-input (e.g.
Cmd/Ctrl+Enteron a textarea): add a local@keydown.meta.enter/@keydown.ctrl.enterhandler on the element. The global handler routes modifier combos to keybindings (e.g.mod+kopens the command palette); element-local Cmd/Ctrl+Enter handlers are still preferred for textarea submit so the registry stays focused on app-level actions. - Prefer single-key shortcuts. The handler supports multi-key sequences via an 800 ms tail-match buffer (longer sequences win), and modifier combos via
mod+x/mod+shift+x(aliasmodresolves to Cmd on Mac, Ctrl elsewhere). Multi-key bindings are reserved for cases where every reasonable single letter already collides. - Gate commands declaratively via the
whenfield — a whenexpr string evaluated againstuseWhenContext()(e.g.'hasActiveItem && activeItemState == "open"'). Add a new key toWhenContextinui/composables/useWhenContext.tsrather than reaching for a JS predicate. - Every command is callable from the command palette (
mod+k/mod+shift+p). Usehelp: falseon internal palette commands to keep them out of<HelpOverlay>, orhelp: '<when>'to scope visibility (e.g.help: 'hubMode'). - Every new
btn-*variant inui/uno.config.tsmust includeoutline-none focus-visible:ring-2 focus-visible:ring-primary-500/40, matching the existingtab-triggershortcut. - The
?help overlay (ui/components/HelpOverlay.vue) auto-renders every registered command grouped by itscategory— keep each commandtitleshort and user-facing.
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.
- 2d ago First seen · 66 lines · 2,139 tokens per session scan A e868beb83fba
ghfs AGENTS.md is an instructions file published in the GitHub repository antfu/ghfs (271 stars, last pushed 2mo ago), licensed MIT. It adds 2,139 tokens to every session, about $0.0107 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-08-30.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.