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/skill-mergenpx skills add rhtevan/agentfs --skill skill-mergegit 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/skill-merge)<a href="https://agentmods.dev/skills/rhtevan/agentfs/skill-merge"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/skill-merge.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00951 |
| Opus 5 | $0.00008 | $0.00476 |
| Sonnet 5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
skill-merge 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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Merge
Copy project-scoped skills into the shared USER skills directory so they become available across all projects and agents.
Natural-Language Signals
| User says | Behavior |
|---|---|
| "merge skills", "copy skills to system" (no names) | Copy all skills from ./.agents/skills/ to ~/.agents/skills/ |
| "merge skill foo", "copy foo and bar to system" | Copy only the named skill(s) |
| "merge skills --force", "overwrite existing" | Overwrite existing USER skills with the same name |
Parameters
| Parameter | Default | Description |
|---|---|---|
project_root |
. (current working directory) |
Project root containing .agents/skills/ |
skill_names |
(all) | Space-separated list of skill directory names to copy. If empty, all skills are copied |
force |
false |
If true, overwrite existing USER skills with the same name |
Prerequisites
./.agents/skills/must exist and contain at least one skill (subdirectory with aSKILL.mdfile).~/.agents/skills/must exist (runagentfs-setupin USER scope if not).
Steps
-
Resolve paths
- Source:
<project_root>/.agents/skills/ - Destination:
~/.agents/skills/
- Source:
-
Build skill list
- If
skill_namesis empty: discover all immediate subdirectories of the source that contain aSKILL.mdfile. - If
skill_namesis provided: validate each name exists as a subdirectory with aSKILL.mdin the source. Report and skip any that don't exist.
- If
-
Copy each skill For each skill in the list:
a. Check if
~/.agents/skills/<name>/already exists.- If it exists and
forceisfalse: Skip — print a warning and do not overwrite. - If it exists and
forceistrue: Overwrite — remove the existing directory first, then copy. - If it does not exist: proceed with copy.
b. Copy the entire skill directory recursively:
cp -r <source>/<name> ~/.agents/skills/<name> - If it exists and
What ships with it
1 file 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.
- 5d ago First seen · 114 lines · 15 tokens per session scan A 34073bfc107b
skill-merge is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 15 tokens to every session and 951 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…