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 skills/rhtevan/agentfs/agentfs-setupnpx skills add rhtevan/agentfs --skill agentfs-setupgit clone --depth 1 https://github.com/rhtevan/agentfsWhat 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.00021 | $0.03015 |
| Opus 5 | $0.00010 | $0.01507 |
| Sonnet 5 | $0.00004 | $0.00603 |
| Haiku 4.5 | $0.00002 | $0.00301 |
Grade A, and why
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 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentFS Setup
Scaffold the .agents/ directory tree and seed foundational files for
AgentFS — a layered, agent-agnostic context structure that works across
AI coding agents.
Overview
| Property | Value |
|---|---|
| Default scope | project |
| Scopes | project (per-repo context) · lite (minimal per-repo) · user (shared library) |
| Scripts | scaffold-dotagents.sh · seed-agents-md.sh · sync-agents-md.sh · verify-setup.sh |
| Design spec | references/design-spec.md |
Scope Definitions
AgentFS operates in two scopes. These definitions are canonical.
| Scope | Root Path | Resolves To | Purpose |
|---|---|---|---|
| USER | ~/.agents/ |
/home/<user>/.agents/ |
Machine-wide shared library: skills and knowledge visible across all projects and agents |
| PROJECT | ./.agents/ |
<repo-root>/.agents/ |
Per-repository agent workspace: identity, profiles, memories, and project-scoped skills |
What Lives Where
| Resource | USER (~/.agents/) |
PROJECT (./.agents/) |
|---|---|---|
skills/ |
✅ shared | ✅ project-specific |
knowledge/ |
✅ shared | ❌ never |
memories/ |
❌ never | ✅ per-agent |
profiles/ |
❌ never | ✅ multi-agent |
SOUL.md |
❌ never | ✅ agent identity |
AGENTS.md |
❌ never | ✅ (at repo root ./) |
index.md |
✅ | ✅ |
log.md |
✅ | ✅ |
Prerequisites: USER Scope Setup
Before running PROJECT scope, ~/.agents/ must exist. There are two
paths to set it up:
Path A: Full Install (recommended)
Clone the published AgentFS repository directly into ~/.agents/:
git clone https://github.com/rhtevan/agentfs.git ~/.agents
This gives the complete skill library, knowledge bundles, and structural scaffolding — ready to use immediately.
What ships with it
20 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.
- CHANGELOG.md 14 KB
- references/design-spec.md 32 KB
- scripts/author-soul.sh 10.0 KB runs code
- scripts/checkpoint.sh 3.5 KB runs code
- scripts/init-git.sh 921 B runs code
- scripts/init-speckit.sh 5.8 KB runs code
- scripts/merge-changelog-entry.sh 3.7 KB runs code
- scripts/merge-log-entry.sh 2.3 KB runs code
- scripts/post-edit.sh 5.5 KB runs code
- scripts/pre-push-scan.sh 9.5 KB runs code
- scripts/regen-skill-index.py 6.1 KB runs code
- scripts/rename-agent-context.sh 3.3 KB runs code
- scripts/scaffold-dotagents.sh 10 KB runs code
- scripts/seed-agents-md.sh 23 KB runs code
- scripts/sync-agents-md.sh 7.7 KB runs code
- scripts/test-agents-md-fidelity.sh 8.0 KB runs code
- scripts/test-checkpoint.sh 5.7 KB runs code
- scripts/test-pre-push-scan.sh 8.8 KB runs code
- scripts/test-soul-authoring.sh 12 KB runs code
- scripts/verify-setup.sh 19 KB runs code
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 · 303 lines · 21 tokens per session scan A edcc162b625b
agentfs-setup is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 3,015 once invoked, about $0.0001 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-31.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…