Big-AGI is an open-source workspace for using multiple AI models through chat and other AI functions. It is intended for engineers, founders, researchers, and other users who want to work with AI personas, model comparisons, image generation, voice, documents, and code-related features. The catalogue entries provide commands, instructions, and a skill for working with Big-AGI.
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 commands/enricoros/big-agi/sync-xai-apigit clone --depth 1 https://github.com/enricoros/big-AGIWrote 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/commands/enricoros/big-agi/sync-xai-api)<a href="https://agentmods.dev/commands/enricoros/big-agi/sync-xai-api"><img src="https://agentmods.dev/badge/commands/enricoros/big-agi/sync-xai-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.1 | $0.00010 | $0.01047 |
| Opus 5 | $0.00005 | $0.00524 |
| Sonnet 5 | $0.00002 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
sync-xai-api 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 6d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review the xAI Responses API implementation:
- xAI wire types:
src/modules/aix/server/dispatch/wiretypes/xai.wiretypes.ts(xAI-specific request schema, tools) - Request adapter:
src/modules/aix/server/dispatch/chatGenerate/adapters/xai.responsesCreate.ts(AIX → xAI Responses API) - Response parser:
src/modules/aix/server/dispatch/chatGenerate/parsers/openai.responses.parser.ts(shared with OpenAI Responses) - Dispatch routing:
src/modules/aix/server/dispatch/chatGenerate/chatGenerate.dispatch.ts(dialect='xai' routing) - OpenAI shared types:
src/modules/aix/server/dispatch/wiretypes/openai.wiretypes.ts(InputItem/OutputItem schemas reused by xAI)
IMPORTANT context:
- We use ONLY the xAI Responses API (
POST /v1/responses). We do NOT use the Chat Completions API (/v1/chat/completions) for xAI anymore. - xAI's Responses API is similar to OpenAI's but has key differences - the skill should find what changed since our last sync.
- Response streaming/parsing reuses the OpenAI Responses parser since the format is compatible.
- We do NOT implement: Files API, Collections Search, Remote MCP tools, Voice Agent API, Image/Video generation, Batch API, or Deferred Completions.
Then take a look at the newest API information available. Try these sources, and be creative if some are blocked:
Primary Sources (guide pages work well with WebFetch despite being JS-rendered):
- Responses API Guide: https://docs.x.ai/docs/guides/chat
- Stateful Responses: https://docs.x.ai/docs/guides/responses-api
- Tools Overview: https://docs.x.ai/docs/guides/tools/overview
- Search Tools (web_search, x_search): https://docs.x.ai/docs/guides/tools/search-tools
- Code Execution Tool: https://docs.x.ai/docs/guides/tools/code-execution-tool
- Function Calling: https://docs.x.ai/docs/guides/function-calling
- Streaming: https://docs.x.ai/docs/guides/streaming-response
- Reasoning: https://docs.x.ai/docs/guides/reasoning
- Structured Outputs: https://docs.x.ai/docs/guides/structured-outputs
- Models & Pricing: https://docs.x.ai/developers/models
- Release Notes: https://docs.x.ai/developers/release-notes
- API Reference: https://docs.x.ai/developers/api-reference#create-new-response
Alternative Sources if primary blocked:
- xAI Python SDK: https://github.com/xai-org/xai-sdk-python
- Web Search for "xai grok api changelog 2026" or "xai responses api new features"
If all blocked: Explain what you attempted and ask user to provide documentation manually.
Live endpoint (extra signal): If .env.api-keys has XAI_API_KEY, fire a real streaming Responses request and inspect the raw SSE - ground-truth for xAI-specific output items, event types, and usage fields that docs lag: POST https://api.x.ai/v1/responses ("stream":true). Never commit or echo the key.
$ARGUMENTS Check carefully for discrepancies between our implementation and the current API docs:
- Request fields: Compare
XAIWire_API_Responses.Request_schemaagainst current docs - any new, changed, or deprecated parameters? - Tool definitions: Compare
XAIWire_Responses_Tools- any new parameters on web_search/x_search/code_interpreter? Any new hosted tool types? - Input/Output item types: Any xAI-specific output items not handled by the shared OpenAI parser (e.g., x_search_call, web_search_call, code_interpreter_call)?
- Streaming events: Any xAI-specific SSE event types beyond what the OpenAI Responses parser handles?
- Response shape: Usage reporting differences, new fields in the response object?
- Adapter logic: Message role mapping, content type handling, system message approach - still correct?
- Include options: Any new values for the
includearray? - Reasoning config: Which models support it and with what values?
Prioritize breaking changes and new capabilities that would improve the user experience.
When making changes, add comments with date: // [xAI, 2026-MM-DD]: explanation
Self-update this skill: After completing the sync, if your research reveals that assumptions in THIS skill file (.claude/commands/aix/sync-xai-api.md) are wrong or outdated - e.g., new APIs we now implement, new tool types added, URLs moved, file paths changed - update this skill file to stay accurate for next time.
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.
- 6d ago First seen · 59 lines · 10 tokens per session scan A fdbd2544852b
sync-xai-api is a command published in the GitHub repository enricoros/big-AGI (7,109 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 1,047 once invoked, about $0.0001 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 commands, from other repositories
AGENTS
Per-command agent-optimized usage and structure guide.
netllm-connect
Wire Cursor, Claude Code, Codex, or Honcho to the local netllm router.
setup
Configure claude-delegator with Codex (GPT) or Gemini MCP servers.
post-claims
Follow the Post Claims SOP in docs/sops/POSTCLAIMSSOP.md.
forge
You are in FORGE MODE. Execute the following.
apex-architect
Use the @apex-architect agent to help the user with the following architectural or debugging matter: $ARGUMENTS.