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-projectsnpx skills add Abilityai/abilities --skill setup-projectsgit 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.00016 | $0.01054 |
| Opus 5 | $0.00008 | $0.00527 |
| Sonnet 5 | $0.00003 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
setup-projects 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 yesterday.
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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Projects
Initialize project and session management for organized multi-session work.
Step 1: Ask Configuration
Use AskUserQuestion:
Question 1: "Where should projects be stored?"
- Options:
- "projects/ folder (Recommended)" - Standard location
- "Custom location" - Specify a different path
Question 2: "Where should session files be stored?"
- Options:
- "sessions/ folder (Recommended)" - Date-based session storage
- "Inside each project" - Project-specific sessions
Step 2: Create Directory Structure
mkdir -p projects
mkdir -p sessions
Step 3: Create Project Index
Write projects/PROJECT_INDEX.md:
# Project Index
Central registry of all projects.
| Project | Status | Created | Last Active | Description |
|---------|--------|---------|-------------|-------------|
| (none yet) | - | - | - | - |
## Status Legend
- **active** - Currently being worked on
- **paused** - On hold, will resume
- **completed** - Finished, archived
- **archived** - No longer relevant
Step 4: Create Session Index
Write sessions/SESSION_INDEX.md:
# Session Index
Date-based session tracking.
| Date | Focus | Projects Touched | Key Outcomes |
|------|-------|------------------|--------------|
| (none yet) | - | - | - |
## Session Folder Format
`YYYY-MM-DD_brief-description/`
## Contents
Each session folder contains work artifacts from that date:
- Drafts and work-in-progress
- Research notes
- Temporary files
- Session summary (optional)
Step 5: Create Project Template
Write projects/.project-template/:
.project-template/
├── README.md # Project overview
├── STATUS.md # Current status and next steps
├── DECISIONS.md # Decision log
└── .gitkeep
README.md template:
# Project: ${PROJECT_NAME}
## Overview
[Brief description of the project]
## Goals
- [ ] Goal 1
- [ ] Goal 2
## Key Files
- `file1.ext` - Description
- `file2.ext` - Description
## Related
- [[Link to related project]]
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.
- yesterday First seen · 192 lines · 16 tokens per session scan A 1442a9875ad8
setup-projects is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 16 tokens to every session and 1,054 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…