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/synthetic-sciences/openscience/together-ainpx skills add synthetic-sciences/openscience --skill together-aigit clone --depth 1 https://github.com/synthetic-sciences/openscienceWrote 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/synthetic-sciences/openscience/together-ai)<a href="https://agentmods.dev/skills/synthetic-sciences/openscience/together-ai"><img src="https://agentmods.dev/badge/skills/synthetic-sciences/openscience/together-ai.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.00055 | $0.05732 |
| Opus 5 | $0.00028 | $0.02866 |
| Sonnet 5 | $0.00011 | $0.01146 |
| Haiku 4.5 | $0.00006 | $0.00573 |
Grade A, and why
together-ai-inference 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 today.
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 — 736 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Together AI — Serverless Inference & Fine-Tuning
Together AI is an AI cloud platform providing serverless inference on 200+ open-source models through an OpenAI-compatible API. It supports chat completions, embeddings, fine-tuning, image generation, and batch processing at https://api.together.xyz/v1.
When to Use Together AI
Use Together AI when:
- You need fast serverless inference on open-source models (Llama, DeepSeek, Qwen, Mistral)
- You want an OpenAI-compatible API so you can swap providers with a single line change
- You need to fine-tune open-source models without managing GPU infrastructure
- You want cost-effective inference with pay-per-token pricing
- You need function calling, JSON mode, or structured outputs from open-source models
- You want batch processing at 50% lower cost for non-urgent workloads
- You need embeddings or image generation alongside chat completions
Use alternatives instead:
| Need | Use Instead |
|---|---|
| Managed LoRA fine-tuning with training platform | Tinker |
| Self-hosted inference with full control | vLLM, TensorRT-LLM |
| Dedicated GPU instances | Lambda Labs, RunPod |
| Serverless GPU with custom containers | Modal |
| Multi-cloud cost optimization | SkyPilot |
| Proprietary models (GPT-4o, Claude) | OpenAI, Anthropic directly |
Credential Setup
Credentials are auto-injected by openscience when connected via the dashboard.
# Verify credentials
[ -n "$TOGETHER_API_KEY" ] && echo "TOGETHER_API_KEY set" || echo "NOT SET"
If not set: add your Together AI key in Customize → Models or export TOGETHER_API_KEY locally.
Quick Start
Install
pip install together openai
Set API Key
import os
os.environ["TOGETHER_API_KEY"] = "your-api-key"
# Or export in shell:
# export TOGETHER_API_KEY="your-api-key"
Get your API key from https://api.together.xyz/settings/api-keys
Basic Chat Completion
from together import Together
client = Together()
response = client.chat.completions.create(
model="meta-llama/Llama-3.3-70B-Instruct-Reference",
messages=[
{"role": "system", "content": "You are a helpful assistant."},
{"role": "user", "content": "Explain gradient descent in one paragraph."},
],
max_tokens=256,
temperature=0.7,
)
print(response.choices[0].message.content)
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.
- today First seen · 736 lines · 55 tokens per session scan A e1830fbce775
together-ai-inference is a skill published in the GitHub repository synthetic-sciences/openscience (3,432 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 5,732 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-09-03.
Other skills, from other repositories
fal
Use when calling a fal.ai endpoint by id to generate image, audio, or video from JS/Python/curl: subscribe vs submit, queue states, ED25519 webhook signature verification, per-call cost, or migrating off @fal-ai/serverless-client. NOT which model or art direction (that is ai-media); NOT the same models on another…
nemotron-retrieval-recipes
Use when planning, debugging, tuning, evaluating, exporting, or deploying public Nemotron embed/rerank retrieval recipes.
data-validation-first
Use this skill before any data analysis, transformation, or modeling. Always inspect and validate the data before drawing conclusions or writing transformations.
input-validation-and-sanitization
Use this skill when implementing any endpoint, form handler, CLI tool, or function that accepts external input. Validate and sanitize all untrusted data before processing — never assume input is safe.
robust-error-handling-in-scripts
Use this skill when writing shell scripts, Python automation, or any unattended batch job. Ensure failures are detected, logged, and handled — never silently ignored.
structured-logging-and-observability
Use this skill when building production services, pipelines, or automation that needs to be debugged, monitored, or audited. Add structured logs, metrics, and health checks before shipping any service.