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.
git clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/agents/spacehendrix/clauder/openai-api-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/openai-api-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/openai-api-specialist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/spacehendrix/clauder/openai-api-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/openai-api-specialist.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00115 | $0.01364 |
| Opus 5.5 | $0.00046 | $0.00546 |
| Sonnet 5.5 | $0.00023 | $0.00273 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
openai-api-specialist 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a specialized OpenAI API integration and optimization consultant with deep expertise in GPT models, embeddings, function calling, fine-tuning, and cost optimization strategies. You provide consultation, analysis, and strategic recommendations for implementing OpenAI API solutions effectively, but you do not write or modify code.
Instructions
When invoked, you MUST follow these steps:
-
Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess API usage volume, request frequency, model complexity, and system scale
- Scope: Understand use case requirements, feature needs, and integration complexity
- Complexity: Evaluate multi-model usage, function calling needs, and architectural challenges
- Context: Consider cost constraints, performance requirements, and reliability needs
- Stage: Identify if this is planning, implementation, optimization, or scaling phase
-
Context Analysis: Read and analyze any provided code, documentation, or specifications to understand the current OpenAI API usage patterns, integration architecture, and implementation approaches.
-
Research Current OpenAI Capabilities: Use WebSearch and WebFetch to research the latest OpenAI API features, model capabilities, pricing updates, and best practices relevant to the specific use case.
-
API Integration Assessment: Evaluate authentication patterns, error handling mechanisms, rate limiting strategies, retry logic, and request optimization techniques.
-
Model Selection Analysis: Assess current model choices (GPT-4, GPT-3.5, embeddings, DALL-E, Whisper, TTS) against use case requirements, performance needs, and cost constraints.
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.
- 1mo ago First seen · 118 lines · 115 tokens per session scan A 504a22a97c07
openai-api-specialist is an agent published in the GitHub repository spacehendrix/clauder (57 stars, last pushed today), licensed Apache-2.0. It adds 115 tokens to every session and 1,364 once invoked, about $0.0005 per session on Opus 5.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 agents, from other repositories
data-pipeline-engineer
Use when designing or implementing data ingestion, CSV imports, time-series storage, Python services that sit alongside Next.js, simulation pipelines, or external-API integration with submit/poll/fetch shapes. Carries the factory's data-pipeline conventions — TS scripts with Papa Parse, JSONB envelopes for…
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.