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 skills add rhtevan/agentfs --skill goose-agentfs-setupgit clone --depth 1 https://github.com/rhtevan/agentfsWrote 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/skills/rhtevan/agentfs/goose-agentfs-setup)<a href="https://agentmods.dev/skills/rhtevan/agentfs/goose-agentfs-setup"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/goose-agentfs-setup/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/skills/rhtevan/agentfs/goose-agentfs-setup"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/goose-agentfs-setup.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.00020 | $0.02541 |
| Opus 5.5 | $0.00008 | $0.01016 |
| Sonnet 5.5 | $0.00004 | $0.00508 |
| Haiku 4.5 | $0.00002 | $0.00254 |
Grade A, and why
goose-agentfs-setup 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 22d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goose AgentFS Setup
Configure Goose to discover and load cross-agent context files, making it
fully compatible with projects that use Claude Code (CLAUDE.md), Cursor
(.cursorrules), Windsurf (.windsurfrules), or GitHub Copilot conventions.
Problem
Goose loads AGENTS.md and .goosehints by default. Many GitHub repos
include CLAUDE.md (the de facto standard from Claude Code) with valuable
project context that Goose silently ignores unless configured.
| Context File | Agent | Goose Default? |
|---|---|---|
AGENTS.md |
AgentFS / Goose | ✅ |
.goosehints |
Goose | ✅ |
CLAUDE.md |
Claude Code | ❌ |
.cursorrules |
Cursor | ❌ |
.windsurfrules |
Windsurf | ❌ |
.github/copilot-instructions.md |
GitHub Copilot | ❌ |
Goose supports loading any context file via the CONTEXT_FILE_NAMES
configuration parameter — it just needs to be told which files to look for.
What This Skill Does
Adds cross-agent context filenames to Goose's CONTEXT_FILE_NAMES
configuration in ~/.config/goose/config.yaml, so Goose automatically
discovers and loads them from both global (~/.config/goose/) and
project-local directories (CWD + subdirectories).
How Context File Loading Works in Goose
Goose's context file loading (load_hints.rs) does the following:
- Global hints: Reads each configured filename from
~/.config/goose/<filename>. WhenAGENTS.mdis in the list, also reads~/.agents/AGENTS.md. - Project hints: Reads each configured filename from CWD up to the git root (or just CWD if not in a git repo).
- Subdirectory hints: As the agent touches files in subdirectories, it discovers and loads configured filenames from those directories too.
- Import support: All context files support
@fileimports for including referenced files inline.
All discovered content is concatenated into the system prompt.
Prerequisites
- Goose installed with
config.yamlsupport (v1.30+) - Config file at
~/.config/goose/config.yaml
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 22d ago Changed ad49a037c7b6
- 23d ago Changed · +30 lines 9aa2b8ba3f1f
- 1mo ago First seen · 305 lines · 20 tokens per session scan A 548f7e5af071
goose-agentfs-setup is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 2,541 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…