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 skill-indexgit 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-index)<a href="https://agentmods.dev/skills/rhtevan/agentfs/skill-index"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/skill-index/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/skill-index"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/skill-index.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.00532 |
| Opus 5.5 | $0.00006 | $0.00213 |
| Sonnet 5.5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
skill-index 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.
What it actually says
Skill Index Generator
Scope guard: This skill is not available in LITE scope projects. LITE scope does not support skills or knowledge bundles. If the target project's AGENTS.md contains
agentfs-scope: lite, refuse with a clear message.
Regenerate index.md for a skills directory by scanning all SKILL.md files.
Skill Location Selection
| User signal | Skills root used |
|---|---|
| (no hint) — "refresh skill index", "index skills" | USER: ~/.agents/skills/ |
| "project skills", "index for project", "local skills" | PROJECT: ./.agents/skills/ |
| Explicit path provided | Use the provided path as-is |
Default to USER. Only use ./.agents/skills/ when the user
specifically calls out project scope.
Steps
- Resolve the skills root — apply location selection rules above.
- Run the canonical index generator:
python3 ~/.agents/skills/agentfs-setup/scripts/regen-skill-index.py <skills_root> - Report — show output (skill count, warnings) to user.
What the script does
- Scans each immediate subdirectory for
SKILL.md - Extracts
name,description,metadata.tagsfrom YAML frontmatter (supports multi-line scalars>,|) - Falls back to first paragraph line if no frontmatter
- Validates: name-directory consistency,
metadata.versionpresence, legacymetadata.signalsabsence - Generates
index.mdsorted reverse-chronologically (newest first) - Exit 0 = clean, exit 1 = warnings found
Verification
-
index.mdexists at the skills root - Every subdirectory with
SKILL.mdhas a corresponding row - Each link resolves to the correct
SKILL.md - Rows sorted newest-first
- No name-mismatch or missing-version warnings
Changelog
See CHANGELOG.md for version history.
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.
- 1mo ago First seen · 63 lines · 14 tokens per session scan A 8c28be1ddcea
skill-index 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 532 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…