Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rhtevan/agentfsnpx agentmods add skills/rhtevan/agentfs/agentfs-profileWrote 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/agentfs-profile)<a href="https://agentmods.dev/skills/rhtevan/agentfs/agentfs-profile"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/agentfs-profile/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/agentfs-profile"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/agentfs-profile.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.00014 | $0.01046 |
| Opus 5.5 | $0.00006 | $0.00418 |
| Sonnet 5.5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
agentfs-profile 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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent FS Profile
Create and manage named agent profiles for multi-agent collaboration within a DotAgents PROJECT scope setup.
Overview
In PROJECT scope, the default agent uses .agents/SOUL.md and
.agents/memories/ at the root level. When multiple agents need to
collaborate on the same project, each additional agent gets its own
named profile under .agents/profiles/<name>/.
What a profile contains
.agents/profiles/<agent-name>/
├── SOUL.md # Agent identity (human-authored)
└── memories/
├── USER.md # Agent's model of the user (agent-learned)
└── MEMORY.md # Agent's learned project facts (agent-learned)
What is shared (NOT in profiles)
Skills are project-scoped and shared across all agents:
.agents/skills/— all agents use the same skills- Knowledge bundles live at
~/.agents/knowledge/(USER scope, shared across projects)
Prerequisites
agentfs-setupmust have been run in PROJECT scope first- Not available in LITE scope — LITE scope does not support agent profiles
(
.agents/profiles/directory must exist).
Usage
From an agent console
The agent should run the script with the profile name:
bash <skill-dir>/scripts/create-profile.sh <profile-name> <project-root>
Examples:
# Create a profile for a specialized coding agent
bash <skill-dir>/scripts/create-profile.sh coder .
# Create a profile for a research agent
bash <skill-dir>/scripts/create-profile.sh researcher .
Natural-language signals
When the user says things like:
- "add an agent called coder"
- "set up a researcher profile"
Extract the profile name and run the script.
After Creation
- AGENTS.md updated — The script automatically registers the new
profile in the Agent Profiles table in
AGENTS.md. Any agent readingAGENTS.mdcan discover the profile and navigate to its SOUL and memories. The registration is idempotent — running the script again for the same profile name skips the table update. profiles/index.mdupdated — The script registers the profile in.agents/profiles/index.mdwith links to bothSOUL.mdandmemories/MEMORY.md, plus a timestamp. Entries are sorted newest- first (reverse chronological order) per the Index Currency guardrail.- Edit
SOUL.md— The user should customize the agent's identity and personality in the profile'sSOUL.md. - Memories auto-populate —
USER.mdandMEMORY.mdare seeded with comment headers. The agent fills them in during conversations. - Skills — No per-profile setup needed. All agents share
.agents/skills/. Knowledge lives at~/.agents/knowledge/(USER scope).
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.
- 1mo ago First seen · 127 lines · 14 tokens per session scan A 5c72f7f1ee5e
agentfs-profile is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,046 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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.