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/abilityai/abilities/setup-indexnpx skills add Abilityai/abilities --skill setup-indexgit clone --depth 1 https://github.com/Abilityai/abilitiesWhat 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.00018 | $0.00585 |
| Opus 5 | $0.00009 | $0.00293 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
setup-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 2d 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
Setup File Index
Initialize file indexing for this workspace.
Step 1: Ask Configuration Questions
Use AskUserQuestion to ask the user:
Question 1: "Which directories should be indexed?"
- Options:
- "Current directory only" - Index only the root
- "All directories (Recommended)" - Full recursive index
- "Specific directories" - Let me specify which ones
Question 2: "What should be excluded from the index?"
- Options:
- "Standard exclusions (Recommended)" - node_modules, .git, pycache, .venv, dist, build
- "Minimal exclusions" - Only .git
- "Custom exclusions" - Let me specify
Step 2: Create Index Configuration
Create memory/index_config.json with the user's choices:
{
"root": ".",
"exclude_patterns": ["node_modules", ".git", "__pycache__", ".venv", "dist", "build", "*.pyc", ".DS_Store"],
"include_sizes": true,
"include_dates": true,
"last_indexed": null
}
Step 3: Generate Initial Index
Run the indexing command based on configuration:
find . -type f \
! -path "*/node_modules/*" \
! -path "*/.git/*" \
! -path "*/__pycache__/*" \
! -path "*/.venv/*" \
! -name "*.pyc" \
! -name ".DS_Store" \
-exec ls -lh {} \; 2>/dev/null | \
awk '{print $9, $5, $6, $7, $8}' | sort
Step 4: Write file_index.md
Create memory/file_index.md with format:
# File Index
Last updated: [ISO timestamp]
## Directory Tree
[tree structure]
## Files by Directory
### /path/to/dir
| File | Size | Modified |
|------|------|----------|
| file.txt | 1.2K | 2025-01-15 |
Step 5: Confirm Setup
Tell the user:
- File index created at
memory/file_index.md - Use
/refresh-indexto update - Use
/search-filesto search
Add to CLAUDE.md if it exists:
## File Index
- Index location: `memory/file_index.md`
- Refresh with: `/refresh-index`
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.
- 2d ago First seen · 92 lines · 18 tokens per session scan A 840daf138ebe
setup-index is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 18 tokens to every session and 585 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-30.
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…