R
rhtevan/agentfs
Shared agent scaffolding with skills, knowledge bundles, and cross-agent context for AI agents (Goose, Hermes, Claude Code, etc.)
★ 2·updated 2026-11-18
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
- Star count
- 2 ★ · rhtevan/agentfs · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-17 · last seen 2026-11-20 · seen 4× · listed by 1 sources
- Score
- score 103 · 2 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
rhtevan/agentfs;first catalogued 2026-11-17;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
permalink: /
Excerpted from the repository README (abridged)
# AgentFS (agent-filesystem)
Shared agent scaffolding with skills, knowledge bundles, and cross-agent context.
Part of the agent-x trilogy:
AgentFS (agent-filesystem) — foundation file structures for agents ← this project
AgentFLOW (agent-flow) — deterministic workflow orchestration
AgentBOX (agent-box) — secure enterprise sandbox for agent sessions
AgentFS is a structured filesystem convention for AI agents (Goose, Hermes, Claude Code, etc.) that enables persistent memory, reusable skills, and shared knowledge across agents and sessions.
## Quick Navigation
| Resource | Path | What's Inside |
| Skills catalog | skills/index.md | All available skills — signal phrases, tags, descriptions |
| Knowledge bundles | knowledge/index.md | Curated knowledge — concepts, patterns, postmortems |
| Deployment profiles | skills/hosted-model-ctl/references/deployment-profiles.md | Self-hosted model profiles — fitting scores, speed, hardware, trade-offs |
| Activity log | log.md | Reverse-chronological change history |
| Design spec | skills/agentfs-setup/references/design-spec.md | Architecture, scope model, layer definitions |
## Scope Definitions
AgentFS operates in three scopes. These definitions are canonical.
| Scope | Root Path | Resolves To | Purpose |
| USER | ~/.agents/ | /home/ /.agents/ | Machine-wide shared library: skills and knowledge visible across all projects and agents |
| PROJECT | ./.agents/ | /.agents/ | Per-repository agent workspace: identity, profiles, memories, and project-scoped skills |
| LITE | ./.agents/ | /.agents/ | Minimal per-repo workspace for small-context models: identity and memories only |
> Rule of thumb: USER scope = ~/.agents/. PROJECT scope = ./.agents/ (CWD). LITE scope = ./.agents/ at a remote path, managed externally.
> This repository is a USER scope AgentFS instance.
## Getting Started
### Step 1: Set Up USER Scope (~/.agents/)
Choose one of two paths:
#### Path A: Full Install (recommended)
Clone this repo directly into ~/.agents/:
bash
git clone https://github.com/rhtevan/agentfs.git ~/.agents
You get the complete skill library, knowledge bundles, and structural
scaffolding — ready to use immediately.
#### Path B: Minimal Install
For a clean, empty ~/.agents/ where you cherry-pick skills:
1. Clone the repo to a staging location:
bash
git clone https://github.com/rhtevan/agentfs.git ~/repos/agentfs
2. Make the staging location visible to your agent (e.g., add
~/repos/agentfs/skills/ to the agent's skill search paths
— see the relevant agent setup skill for details).
3. Ask your agent to run the agentfs-setup skill with USER scope:
> "Set up AgentFS in USER scope"
The agent will load the agentfs-setup skill and scaffold an
empty ~/.agents/ with skills/, knowledge/, index.md,
and log.md.
4. Cherry-pick specific skills using the skill-merge skill or
manual copy.
### Step 2: Configure Your Agent
#### With Goose
Load the goose-agentfs-setup skill to configure Goose for AgentFS:
Context files: Registers CLAUDE.md, .goosehints, etc. in
Goose's CONTEXT_FILE_NAMES
System prompt optimization: Generates a custom system.md that
places AGENTS.md rules at the primacy zone (top of system prompt)
for improved compliance on smaller models. Includes drift detection
Shared agent scaffolding with skills, knowledge bundles, and cross-agent context.
Part of the agent-x trilogy:
AgentFS (agent-filesystem) — foundation file structures for agents ← this project
AgentFLOW (agent-flow) — deterministic workflow orchestration
AgentBOX (agent-box) — secure enterprise sandbox for agent sessions
AgentFS is a structured filesystem convention for AI agents (Goose, Hermes, Claude Code, etc.) that enables persistent memory, reusable skills, and shared knowledge across agents and sessions.
## Quick Navigation
| Resource | Path | What's Inside |
| Skills catalog | skills/index.md | All available skills — signal phrases, tags, descriptions |
| Knowledge bundles | knowledge/index.md | Curated knowledge — concepts, patterns, postmortems |
| Deployment profiles | skills/hosted-model-ctl/references/deployment-profiles.md | Self-hosted model profiles — fitting scores, speed, hardware, trade-offs |
| Activity log | log.md | Reverse-chronological change history |
| Design spec | skills/agentfs-setup/references/design-spec.md | Architecture, scope model, layer definitions |
## Scope Definitions
AgentFS operates in three scopes. These definitions are canonical.
| Scope | Root Path | Resolves To | Purpose |
| USER | ~/.agents/ | /home/ /.agents/ | Machine-wide shared library: skills and knowledge visible across all projects and agents |
| PROJECT | ./.agents/ | /.agents/ | Per-repository agent workspace: identity, profiles, memories, and project-scoped skills |
| LITE | ./.agents/ | /.agents/ | Minimal per-repo workspace for small-context models: identity and memories only |
> Rule of thumb: USER scope = ~/.agents/. PROJECT scope = ./.agents/ (CWD). LITE scope = ./.agents/ at a remote path, managed externally.
> This repository is a USER scope AgentFS instance.
## Getting Started
### Step 1: Set Up USER Scope (~/.agents/)
Choose one of two paths:
#### Path A: Full Install (recommended)
Clone this repo directly into ~/.agents/:
bash
git clone https://github.com/rhtevan/agentfs.git ~/.agents
You get the complete skill library, knowledge bundles, and structural
scaffolding — ready to use immediately.
#### Path B: Minimal Install
For a clean, empty ~/.agents/ where you cherry-pick skills:
1. Clone the repo to a staging location:
bash
git clone https://github.com/rhtevan/agentfs.git ~/repos/agentfs
2. Make the staging location visible to your agent (e.g., add
~/repos/agentfs/skills/ to the agent's skill search paths
— see the relevant agent setup skill for details).
3. Ask your agent to run the agentfs-setup skill with USER scope:
> "Set up AgentFS in USER scope"
The agent will load the agentfs-setup skill and scaffold an
empty ~/.agents/ with skills/, knowledge/, index.md,
and log.md.
4. Cherry-pick specific skills using the skill-merge skill or
manual copy.
### Step 2: Configure Your Agent
#### With Goose
Load the goose-agentfs-setup skill to configure Goose for AgentFS:
Context files: Registers CLAUDE.md, .goosehints, etc. in
Goose's CONTEXT_FILE_NAMES
System prompt optimization: Generates a custom system.md that
places AGENTS.md rules at the primacy zone (top of system prompt)
for improved compliance on smaller models. Includes drift detection
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/rhtevan-agentfs/)
- Source
- github · https://github.com/rhtevan/agentfs
- Browse by field
- Open source
- Traction
- 2 ★
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.