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 skills add 0xatd/cheaptokens-skills --skill venice-authgit clone --depth 1 https://github.com/0xatd/cheaptokens-skillsWrote 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/0xatd/cheaptokens-skills/venice-auth)<a href="https://agentmods.dev/skills/0xatd/cheaptokens-skills/venice-auth"><img src="https://agentmods.dev/badge/skills/0xatd/cheaptokens-skills/venice-auth/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/skills/0xatd/cheaptokens-skills/venice-auth"><img src="https://agentmods.dev/badge/skills/0xatd/cheaptokens-skills/venice-auth.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.00057 | $0.02188 |
| Opus 5 | $0.00028 | $0.01094 |
| Sonnet 5 | $0.00011 | $0.00438 |
| Haiku 4.5 | $0.00006 | $0.00219 |
Grade B, and why
venice-auth scanned grade B with 2 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 11d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const res = await fetch('https://api.venice.ai/api/v1/chat/completions', { method: 'POST', Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://api.venice.ai/api/v1/chat/completions \ How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Venice Authentication
Every Venice endpoint accepts one of two auth schemes, declared in the OpenAPI spec as BearerAuth and siwx. Both are first-class — pick whichever fits the deployment.
Use when
- You're making your first call to
api.venice.ai. - You're building a server-side integration (usually Bearer) or an agent / no-account wallet flow (x402).
- You hit
401 Authentication failedand need to check header format. - You're implementing SIWE signing manually instead of using the SDK.
Option A — Bearer API key
Authorization: Bearer <VENICE_API_KEY>
- Create keys at https://venice.ai/settings/api or via
venice-api-keys. - Keys carry
consumptionLimits(USD and/or DIEM caps) andapiKeyType(ADMINorINFERENCE). - Billing draws from DIEM (staked), USD balance, and bundled credits in order.
- Key types determine which endpoints are reachable — only
ADMINkeys can manage other keys.
curl https://api.venice.ai/api/v1/chat/completions \
-H "Authorization: Bearer $VENICE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "zai-org-glm-5-1",
"messages": [{"role":"user","content":"hello"}]
}'
Use the Bearer scheme when you have a Venice account, want usage analytics (/billing/usage-analytics), want to issue scoped child keys, or need DIEM / bundled credit priority.
Option B — x402 wallet (SIWE)
Authenticate with an Ethereum wallet. No account needed. Pay per request in USDC on Base (chain ID 8453). Balance lives under your wallet address and is consumed automatically.
Header
X-Sign-In-With-X: <base64(json)>
Where the decoded JSON is:
{
"address": "0x... (checksummed)",
"message": "<SIWE message string from SiweMessage.prepareMessage()>",
"signature": "0x... (hex)",
"timestamp": 1712659200000,
"chainId": 8453
}
SIWE message fields (EIP-4361)
| Field | Value |
|---|---|
domain |
One of the allow-listed Venice domains: venice.ai, api.venice.ai, outerface.venice.ai, preview.venice.ai, staging.venice.ai (plus localhost in dev). The server's own generated challenge uses api.venice.ai. |
uri |
Matching https://<domain> URL. |
version |
"1" |
address |
the wallet's checksummed address |
statement |
"Sign in to Venice AI" (what the server's generated challenge uses — any string is accepted, this one keeps consent UX consistent). |
nonce |
random 16-char hex, single-use per wallet |
issuedAt / expirationTime |
ISO-8601. Server enforces a hard 5-minute window from issuedAt (expirationTime is informational only). |
chainId |
8453 — accepted as number (8453), numeric string ("8453"), or CAIP-2 ("eip155:8453"). |
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.
- 11d ago First seen · 184 lines · 57 tokens per session scan B c833b44c6140
venice-auth is a skill published in the GitHub repository 0xatd/cheaptokens-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 2,188 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
t2000-sui-platform
Sui platform patterns for throughput and gas — Address Balances (SIP-58) accumulators that let ONE address run concurrent txs, and gasless stablecoin transfers that remove the "you need SUI to send USDC" wall. Includes the eligibility gotchas that cause misleading failures (0.01 minimum, the dust-remainder floor…
x402-server
Add x402 payment protection to any API endpoint using @dexterai/x402/server. Trigger when the user wants to monetize an API, add a paywall, accept crypto payments on their server, set up Stripe settlement, configure dynamic pricing, create access passes, or enable sponsored access (ads for agents).
bridgenode
BridgeNode MCP wrapper — stdio MCP server proxying to remote streamable-HTTP endpoint with automatic x402 payment on Solana USDC. No API keys. Use when an agent needs LLM inference through MCP (Claude Code, Cursor, etc.) and has no provider API key.
groq-inference
Ultra-fast LLM inference on custom LPU hardware. OpenAI-compatible API at api.groq.com. Lowest latency in the industry (500-1000+ tok/s). Supports chat completions, vision, audio (Whisper STT + TTS), tool calling, JSON mode, and streaming. Free tier available. Inference only — no training.
web3-fullstack-packaged-build
Systematic full-stack Web3 build with mandatory packaging and delivery phase.
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain…