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/archive-projectnpx skills add Abilityai/abilities --skill archive-projectgit 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.00009 | $0.00362 |
| Opus 5 | $0.00005 | $0.00181 |
| Sonnet 5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
archive-project 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
Archive Project
Archive a completed or inactive project.
Arguments
$ARGUMENTS - The project name to archive
Step 1: Verify Project Exists
Check projects/$PROJECT_NAME/ exists.
If not found:
- List available projects
- Ask user to confirm the correct name
Step 2: Read Current Status
Read projects/$PROJECT_NAME/STATUS.md to understand current state.
Step 3: Confirm Archive
Show user:
- Project name
- Current status
- Last updated date
- Brief summary
Ask for confirmation before archiving.
Step 4: Update Status
Update projects/$PROJECT_NAME/STATUS.md:
**Current Status**: archived
**Last Updated**: [Today's date]
**Archived**: [Today's date]
## Archive Reason
[User-provided or "Project completed" default]
## Final State
[Summary of what was accomplished]
Step 5: Move to Archive
mkdir -p projects/_archive
mv "projects/$PROJECT_NAME" "projects/_archive/$PROJECT_NAME"
Step 6: Update Project Index
Update projects/PROJECT_INDEX.md:
- Change status to "archived"
- Add archive date
Or move entry to an "Archived Projects" section.
Step 7: Report
Tell user:
- Project archived to
projects/_archive/[name]/ - STATUS.md updated with archive details
- Project Index updated
- Can be restored by moving back to
projects/
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 · 79 lines · 9 tokens per session scan A facb58c0ccde
archive-project is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 15d ago), licensed MIT. It adds 9 tokens to every session and 362 once invoked, about $0.0000 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…