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 instructions/veniceai/skills/agents-mdgit clone --depth 1 https://github.com/veniceai/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/instructions/veniceai/skills/agents-md)<a href="https://agentmods.dev/instructions/veniceai/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/veniceai/skills/agents-md.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.00307 | $0.00307 |
| Opus 5 | $0.00153 | $0.00153 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
skills AGENTS.md scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Treat its endpoint tables, params, and curl/SDK examples as the source of truth. What it actually says
Agent guide — venice-skills
This repo is the authoritative Venice API reference, kept in sync with the Venice OpenAPI spec. When you build anything that touches the Venice API — guides, code samples, sandboxes, scripts — load the relevant skill instead of guessing endpoints, params, or model slugs.
Read this first
README.md— the full skill catalog and how the format works.skills/<name>/SKILL.md— one self-contained reference per API surface (auth, chat, image, video, audio, embeddings, billing, errors, etc.).
How to use
- Pick the skill matching the surface you're documenting (e.g.
venice-image-generate,venice-video,venice-chat,venice-text-routing). - Treat its endpoint tables, params, and curl/SDK examples as the source of truth.
- If a skill looks stale vs. the live API, flag it — don't invent.
scripts/sync_from_swagger.pychecks for drift against the spec.
Authoring
New skill? Copy template/ to skills/<name>/ and follow CONTRIBUTING.md.
Source of truth: the Venice OpenAPI spec + public docs at https://docs.venice.ai. For the broader product/surface picture (every endpoint mapped to user actions), see the sibling
venice-kb/repo.
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.
- 5d ago First seen · 21 lines · 307 tokens per session scan A 96b8c7258e71
skills AGENTS.md is an instructions file published in the GitHub repository veniceai/skills (139 stars, last pushed 4d ago), licensed MIT. It adds 307 tokens to every session, about $0.0015 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.