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/omnigentx/jarvis/claude-apinpx skills add omnigentx/jarvis --skill claude-apigit clone --depth 1 https://github.com/omnigentx/jarvisWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/omnigentx/jarvis/claude-api)<a href="https://agentmods.dev/skills/omnigentx/jarvis/claude-api"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/claude-api.svg" alt="Measured on agentmods" height="20"></a>What 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.00193 | $0.08162 |
| Opus 5 | $0.00097 | $0.04081 |
| Sonnet 5 | $0.00039 | $0.01632 |
| Haiku 4.5 | $0.00019 | $0.00816 |
Grade A, and why
claude-api scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Raw HTTP** (`curl`, `requests`, `fetch`, `httpx`, etc.) — only when the user explicitly asks for cURL/REST/raw HTTP, the project is a shell/cURL project, or the language has no official SDK. This is a copy
95% identical to claude-api — 35 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building LLM-Powered Applications with Claude
This skill helps you build LLM-powered applications with Claude. Choose the right surface based on your needs, detect the project language, then read the relevant language-specific documentation.
Before You Start
Scan the target file (or, if no target file, the prompt and project) for non-Anthropic provider markers — import openai, from openai, langchain_openai, OpenAI(, gpt-4, gpt-5, file names like agent-openai.py or *-generic.py, or any explicit instruction to keep the code provider-neutral. If you find any, stop and tell the user that this skill produces Claude/Anthropic SDK code; ask whether they want to switch the file to Claude or want a non-Claude implementation. Do not edit a non-Anthropic file with Anthropic SDK calls.
Output Requirement
When the user asks you to add, modify, or implement a Claude feature, your code must call Claude through one of:
- The official Anthropic SDK for the project's language (
anthropic,@anthropic-ai/sdk,com.anthropic.*, etc.). This is the default whenever a supported SDK exists for the project. - Raw HTTP (
curl,requests,fetch,httpx, etc.) — only when the user explicitly asks for cURL/REST/raw HTTP, the project is a shell/cURL project, or the language has no official SDK.
Never mix the two — don't reach for requests/fetch in a Python or TypeScript project just because it feels lighter. Never fall back to OpenAI-compatible shims.
Never guess SDK usage. Function names, class names, namespaces, method signatures, and import paths must come from explicit documentation — either the {lang}/ files in this skill or the official SDK repositories or documentation links listed in shared/live-sources.md. If the binding you need is not explicitly documented in the skill files, WebFetch the relevant SDK repo from shared/live-sources.md before writing code. Do not infer Ruby/Java/Go/PHP/C# APIs from cURL shapes or from another language's SDK.
What ships with it
44 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.
- csharp/claude-api.md 14 KB
- curl/examples.md 6.3 KB
- curl/managed-agents.md 7.2 KB
- go/claude-api.md 14 KB
- go/managed-agents/README.md 18 KB
- java/claude-api.md 15 KB
- java/managed-agents/README.md 16 KB
- LICENSE.txt 11 KB
- php/claude-api.md 11 KB
- php/managed-agents/README.md 13 KB
- python/claude-api/batches.md 5.0 KB
- python/claude-api/files-api.md 3.9 KB
- python/claude-api/README.md 12 KB
- python/claude-api/streaming.md 5.1 KB
- python/claude-api/tool-use.md 17 KB
- python/managed-agents/README.md 9.6 KB
- ruby/claude-api.md 2.9 KB
- ruby/managed-agents/README.md 9.9 KB
- shared/agent-design.md 8.1 KB
- shared/error-codes.md 7.5 KB
- shared/live-sources.md 17 KB
- shared/managed-agents-api-reference.md 24 KB
- shared/managed-agents-client-patterns.md 9.2 KB
- shared/managed-agents-core.md 14 KB
- shared/managed-agents-environments.md 11 KB
- shared/managed-agents-events.md 9.4 KB
- shared/managed-agents-memory.md 9.4 KB
- shared/managed-agents-multiagent.md 6.4 KB
- shared/managed-agents-onboarding.md 8.1 KB
- shared/managed-agents-outcomes.md 6.0 KB
- shared/managed-agents-overview.md 9.6 KB
- shared/managed-agents-self-hosted-sandboxes.md 9.7 KB
- shared/managed-agents-tools.md 14 KB
- shared/managed-agents-webhooks.md 4.9 KB
- shared/model-migration.md 79 KB
- shared/models.md 8.0 KB
- shared/prompt-caching.md 9.6 KB
- shared/tool-use-concepts.md 17 KB
- typescript/claude-api/batches.md 2.5 KB
- typescript/claude-api/files-api.md 2.2 KB
- typescript/claude-api/README.md 9.7 KB
- typescript/claude-api/streaming.md 5.5 KB
- typescript/claude-api/tool-use.md 15 KB
- typescript/managed-agents/README.md 9.2 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.
- 4d ago First seen · 326 lines · 193 tokens per session scan A 47d67884657f
claude-api is a skill published in the GitHub repository omnigentx/jarvis (36 stars, last pushed 7d ago), licensed MIT. It adds 193 tokens to every session and 8,162 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 95% identical to claude-api, differing in 35 lines, and is treated as a copy.
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…