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/volcengine/volcengine-skills/gemini-mdgit clone --depth 1 https://github.com/volcengine/volcengine-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/volcengine/volcengine-skills/gemini-md)<a href="https://agentmods.dev/instructions/volcengine/volcengine-skills/gemini-md"><img src="https://agentmods.dev/badge/instructions/volcengine/volcengine-skills/gemini-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.00497 | $0.00497 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
volcengine-skills GEMINI.md 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 2d 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.
What it actually says
Volcengine Skills (for Gemini CLI)
This extension installs the Volcengine core plugin. For Volcengine tasks, load the matching core
skill from plugins/volcengine-core/skills/<skill-name>/SKILL.md.
Core skills:
volcengine-cli— operate cloud resources with theveCLI.volcengine-troubleshooting— diagnose Volcengine errors and resource issues.volcengine-knowledge-search— search and retrieve official Volcengine documentation.volcengine-find-skills— list all core and optional skills for the agent to select and install.
Optional catalogued skills:
volcengine-sale— service support plugin; route Volcengine sale intents and delegate to product skills.volcengine-prepare— service support plugin; analyze a repository and recommend a deployment shape.volcengine-deploy— service support plugin; deploy an application to Volcengine.volcengine-iac— service support plugin; manage infrastructure with Terraform.volcengine-tosutil— storage plugin; manage TOS buckets and objects.volcengine-db-supabase— database plugin; manage Volcengine AI-native BaaS (AIDAP).volcengine-vefaas— containers and middleware plugin; manage veFaaS applications.volcengine-compliance— security plugin; assess and improve compliance posture.volcengine-landing-zone— identity and access control plugin; establish landing zones and baselines.volcengine-api— service support plugin; query Volcengine API specifications.volcengine-sdk-generator— service support plugin; generate runnable SDK examples.
When an optional skill is needed, or an active Volcengine task exceeds the capabilities of the
currently loaded or installed skills, load volcengine-find-skills and follow its discovery and
installation workflow. Do not treat a catalogued optional skill as installed merely because its
source exists inside another plugin in this repository. Install the exact selected skills, not
their owning plugins.
Trigger on Volcengine / 火山引擎 / 火山 keywords, ve commands, or
VOLCENGINE_ACCESS_KEY / VOLCENGINE_SECRET_KEY / VOLCENGINE_REGION usage.
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.
- 2d ago First seen · 35 lines · 497 tokens per session scan A 06bca247676c
volcengine-skills GEMINI.md is an instructions file published in the GitHub repository volcengine/volcengine-skills (18 stars, last pushed 7d ago), licensed MIT. It adds 497 tokens to every session, about $0.0025 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-01.
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.