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/emdashcodes/claude-code-plugins/claude-agent-sdknpx skills add emdashcodes/claude-code-plugins --skill claude-agent-sdkgit clone --depth 1 https://github.com/emdashcodes/claude-code-pluginsWhat 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.00052 | $0.02155 |
| Opus 5 | $0.00026 | $0.01077 |
| Sonnet 5 | $0.00010 | $0.00431 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
claude-agent-sdk 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.
How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Agent SDK Development
Overview
This skill provides comprehensive documentation and development guidance for building applications with the Claude Agent SDK. Use this skill when working with Claude Agent SDK based applications, implementing SDK features, or answering questions about SDK capabilities in both Python and TypeScript.
The Claude Agent SDK enables building conversational AI agents with access to tools, multi-turn sessions, streaming, structured outputs, and extensibility through Skills, Plugins, Slash Commands, and Subagents.
When to Use This Skill
Activate this skill when:
- Building new applications using the Claude Agent SDK
- Implementing SDK features (sessions, permissions, streaming, structured outputs)
- Adding extensibility (Skills, Plugins, Slash Commands, Subagents, MCP)
- Integrating custom tools or external APIs
- Troubleshooting SDK issues or migration from legacy implementations
- Answering questions about SDK capabilities, APIs, or best practices
- Setting up hosting and deployment for SDK applications
- Implementing cost tracking and usage monitoring
Quick Start
API References
The SDK is available in both Python and TypeScript. For detailed API documentation, reference:
- Python API:
references/agent-sdk_python.md - TypeScript API:
references/agent-sdk_typescript.md
Getting Started
For SDK overview and core concepts, reference:
- Overview:
references/agent-sdk_overview.md
Core Features
1. Session Management
Sessions enable multi-turn conversations with state persistence. To implement sessions:
Reference: references/agent-sdk_sessions.md
Key concepts:
- Creating and managing sessions
- Persisting conversation state
- Resuming sessions across requests
- Session lifecycle and cleanup
When to reference: When implementing multi-turn conversations, state persistence, or conversation continuity.
2. Permissions System
The SDK includes a permissions system for controlling tool access and user approval flows.
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/agent-sdk_cost-tracking.md 8.7 KB
- references/agent-sdk_custom-tools.md 11 KB
- references/agent-sdk_hosting.md 7.0 KB
- references/agent-sdk_mcp.md 4.8 KB
- references/agent-sdk_migration-guide.md 7.5 KB
- references/agent-sdk_modifying-system-prompts.md 11 KB
- references/agent-sdk_overview.md 7.6 KB
- references/agent-sdk_permissions.md 10 KB
- references/agent-sdk_plugins.md 7.3 KB
- references/agent-sdk_python.md 54 KB
- references/agent-sdk_sessions.md 4.7 KB
- references/agent-sdk_skills.md 8.6 KB
- references/agent-sdk_slash-commands.md 9.0 KB
- references/agent-sdk_streaming-vs-single-mode.md 5.4 KB
- references/agent-sdk_structured-outputs.md 7.5 KB
- references/agent-sdk_subagents.md 9.1 KB
- references/agent-sdk_todo-tracking.md 3.7 KB
- references/agent-sdk_typescript.md 39 KB
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 · 345 lines · 52 tokens per session scan A 12cb5a665f76
claude-agent-sdk is a skill published in the GitHub repository emdashcodes/claude-code-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,155 once invoked, about $0.0003 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.