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/doctornpx skills add Abilityai/abilities --skill doctorgit 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.00048 | $0.29184 |
| Opus 5 | $0.00024 | $0.14592 |
| Sonnet 5 | $0.00010 | $0.05837 |
| Haiku 4.5 | $0.00005 | $0.02918 |
Grade B, and why
doctor 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
# Container-only config: the Trinity base image bakes ~/.claude/settings.json with How it starts
The opening of the file, as written. The whole thing — 2,214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Doctor
ℹ️ 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.doctor vX.Y — recent: <summary>. Then proceed.
Create a personal medical-records and health-management agent powered by Claude Code and compatible with Trinity for remote deployment, scheduling, and orchestration.
What you'll get:
- A private repository for one person's health records — PDFs, scans, lab reports, genetic data
- A first-run skill that analyzes existing documents and bootstraps a structured profile (current meds, conditions, lab history)
- Ongoing skills for ingestion, memory upkeep, lab-trend analysis, doctor-visit prep, and supplement/interaction checks
- Multi-language extraction (handles mixed-language document sets)
- Trinity dashboard surfacing key health metrics
Built by Ability.ai — the agent orchestration platform.
This agent is designed for a single individual managing their own records, not for clinics. PHI lives in the user's own repo; nothing is shared by default.
STEP 1: Determine Destination
If the user passed a path as an argument, use it as $destination and skip ahead to STEP 2.
Otherwise, defer the path choice until after STEP 3 (agent name) — the destination defaults to ~/[agent-name]. For now, ask only about the container:
Use AskUserQuestion:
- Question: "Where should this agent live?"
- Header: "Location"
- Options:
~/[agent-name]— home directory (recommended)./[agent-name]— current directory- Custom path
Store the choice as $container. Do not create the directory yet — the agent name comes next.
STEP 2: Patient Identity
Use AskUserQuestion:
- Question: "Who is this agent for? Share the patient's name and any short context that will help the agent prioritize correctly (age range, known major conditions, anything it should always keep in mind)."
- Header: "Patient"
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 · 2,214 lines · 48 tokens per session scan B ee38a0195669
doctor is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 48 tokens to every session and 29,184 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…