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/adjustnpx skills add Abilityai/abilities --skill adjustgit 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.00045 | $0.02509 |
| Opus 5 | $0.00023 | $0.01255 |
| Sonnet 5 | $0.00009 | $0.00502 |
| Haiku 4.5 | $0.00005 | $0.00251 |
Grade B, and why
adjust-agent scanned grade B with 1 finding 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls CLAUDE.md 2>/dev/null && ls -d .claude/skills 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adjust Agent
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.adjust-agent vX.Y — recent: <summary>. Then proceed.
Transition an existing agent to a better state. This is the apply half of the review/adjust pair: it invokes /review-agent (a read-only audit) to find issues, then proposes exact before/after diffs, gets approval, and applies them. Works like /adjust-playbook, but for the agent as a whole.
When to Use
- User says "review this agent" or "improve my agent"
- User says "add a dependency graph" or "set up schedules"
- User says "make this agent Trinity-ready"
- After scaffolding an agent and wanting to harden it
- Periodic health check on an established agent
Step 1: Locate and Read the Agent
If $0 (path) provided, use it. Otherwise, assume current working directory.
Verify it's an agent:
ls CLAUDE.md 2>/dev/null && ls -d .claude/skills 2>/dev/null
If CLAUDE.md doesn't exist, ask for the correct path.
Read all agent artifacts (skip any that don't exist — their absence is itself a finding):
CLAUDE.mdREADME.md,ARCHITECTURE.md,TARGET-ARCHITECTURE.mdtemplate.yaml.env.example.gitignore.mcp.json.templateor.mcp.json- All
SKILL.mdfiles:find .claude/skills -name "SKILL.md" 2>/dev/null - Any subagents:
ls .claude/agents/*.md 2>/dev/null - Top-level file listing:
ls -la
Parse and display the agent's current state:
## Current Agent: [name]
**Identity**: [one-line summary or "not defined"]
**Skills**: [count] — [list names]
**Dependency Graph**: [present / missing]
**Docs**: README [✓/✗] · ARCHITECTURE [✓/✗] · TARGET-ARCHITECTURE [✓/✗]
**Recommended Schedules**: [present / missing]
**Guidelines**: [count or "none"]
**Trinity Ready**: [yes / partially / no]
Step 2: Determine What to Change
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 · 257 lines · 45 tokens per session scan B c34f1c741af1
adjust-agent is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 45 tokens to every session and 2,509 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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…