Install
$ agentstack add skill-joeylu-runtime-free-llm-integration-skills-skill-llm-openai ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill LLM OpenAI
Purpose
Define how an agent integrates a model already named by the user or host project. This skill does not recommend, approve, rank, or automatically replace models during ordinary implementation.
Read Order
Read shared contracts first:
../_shared/route-key-schema.md../_shared/model-catalog-schema.md../_shared/pricing-matrix-schema.md../_shared/capability-matrix-schema.md../_shared/connection-profile-schema.md../_shared/request-url-matrix-schema.md../_shared/request-envelope.md../_shared/response-envelope.md../_shared/error-contract.md../_shared/progress-contract.md../_shared/ui-binding.md../_shared/sync-policy.md../_shared/logging-fields.md
Then read:
references/connection-profiles.mdreferences/request-urls.mdreferences/model-catalog.mdreferences/pricing-matrix.mdreferences/capability-matrix.md- the transport for the requested kind
references/logging-contract.mdwhen logging is implementedreferences/model-sync.mdonly for an explicit update or verification task
Read references/hosted-tools.md when provider-hosted tools are requested.
Runtime Rules
- Send the exact documented model ID. This skill currently maintains rules for
gpt-5.6-sol,gpt-5.6-terra,gpt-5.6-luna, andgpt-image-2. - Do not replace a requested model with another model or moving alias.
- Resolve connection profile, request kind, API surface, API version, endpoint kind, full route key, base URL, and request URL before capability lookup.
- Match capabilities by the exact full
RouteKeyrow, including API version and endpoint kind. - Prefer no surface implicitly: use the surface required by the project. Responses and Chat Completions have different payloads and continuation rules.
- Use
gpt-image-2through the direct Image API rows. Responses hosted image generation is a separate tool flow whose main model is a GPT model. - Reject requested fields marked
unsupportedorunknown; do not silently drop or translate them to another surface. - Keep caller-defined functions in
Toolsand provider-hosted tools inHostedTools. - Preserve response item IDs, call IDs, required linkage, encrypted reasoning items, and assistant
phasewhen continuing a documented stateful flow. - Never expose raw chain-of-thought. Map visible summaries to
ReasoningSummaryand opaque state toReasoningItemsor provider metadata. - Store API-key references only. Never write secrets, authorization headers, MCP credentials, or signed URLs into these files or normal logs.
- Use
pricing-matrix.mdfor estimates, including context bands and cache charges.
Request Flow
- Read the requested provider, region, model, and request kind from the host project or user.
- Resolve the connection profile and exact request URL row.
- Resolve the exact catalog and capability rows.
- Validate every optional field before constructing the request.
- Apply the matching transport.
- Normalize the provider response, errors, progress, and logs through the shared contracts.
OpenAI Field Mapping
- Responses
reasoning.effortand Chat Completionsreasoning_effortuse the values recorded in the capability matrix. TextVerbositymaps to Responsestext.verbosityor Chat Completionsverbosityonly where verified.- Responses
reasoning.mode,reasoning.context, andprevious_response_idare Responses-only fields. - Responses structured output maps through
text.format; Chat Completions maps throughresponse_format. CacheKeymaps toprompt_cache_keywhere verified; explicit cache controls require the documented Responses mapping.
Out of Scope
- ChatGPT consumer configuration
- Apps SDK or Agents SDK orchestration
- Realtime/audio integration
- fine-tuning
- model ranking or model permission policy
- non-OpenAI providers
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: joeylu
- Source: joeylu/runtime-free-llm-integration-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.