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 VKirill/claude-lane-stack --skill yandex-cloudgit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/yandex-cloud)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/yandex-cloud"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/yandex-cloud/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/vkirill/claude-lane-stack/yandex-cloud"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/yandex-cloud.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 20 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00405 | $0.03123 |
| Opus 5 | $0.00202 | $0.01562 |
| Sonnet 5 | $0.00081 | $0.00625 |
| Haiku 4.5 | $0.00040 | $0.00312 |
Grade A, and why
yandex-cloud 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 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.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Version Requirements (May 2026)
Canonical sources:
- Docs repo: https://github.com/yandex-cloud/docs (markdown source for yandex.cloud/ru/docs)
- Public mirror: https://yandex.cloud/ru/docs · https://yandex.cloud/en/docs
- yc CLI: latest stable from https://storage.yandexcloud.net/yandexcloud-yc/install.sh (rolling release)
- Terraform provider:
yandex-cloud/yandexv0.115.x+ - S3 endpoint:
https://storage.yandexcloud.net(S3 v4 sig) - Cloud API gRPC endpoint:
*.api.cloud.yandex.net:443
Managed service versions (May 2026):
- Managed PostgreSQL: 14/15/16/17 (default new clusters)
- Managed MySQL: 5.7/8.0/8.4
- Managed Redis: 6.2/7.0/7.2
- Managed ClickHouse: latest LTS
- Managed Kubernetes: 1.27 → 1.31 (default)
- Managed Kafka: 3.x
Always confirm version pins via yc managed-postgresql cluster list-hosts etc. — never assume.
Usage
Loaded automatically when its description matches the active task. Read only the reference section you need — full documentation lives in the canonical repo above (this skill is a navigator, not a copy).
Use this skill when
- Provisioning, migrating to, or operating workloads on Yandex Cloud
- Working with the
ycCLI: profiles, federations, service accounts, IAM tokens - Setting up Managed Service for PostgreSQL / MySQL / Redis / ClickHouse / MongoDB / Kafka / Greenplum
- Using Object Storage (S3-compatible) — bucket policy, lifecycle, presigned URLs, CORS
- Designing VPC: folders/clouds, networks, subnets, security groups, NAT gateways, peering
- Managed Service for Kubernetes — node groups, autoscaling, network policies, ALB Ingress
- IAM design — service accounts, roles, federations (SAML/OIDC), OAuth tokens
- Storing credentials in Lockbox; serving secrets to VMs/k8s/serverless via metadata
- Cloud Functions / Serverless Containers / API Gateway / Triggers
- Cost optimisation, billing alerts, committed-use discounts
- Migrating from self-hosted (Ubuntu + PostgreSQL + Redis on a single box) to managed YC services
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/compute.md 4.1 KB
- references/iam-auth.md 5.0 KB
- references/kubernetes.md 6.0 KB
- references/load-balancer.md 4.7 KB
- references/managed-databases.md 5.7 KB
- references/migration.md 6.8 KB
- references/object-storage.md 4.7 KB
- references/observability.md 4.8 KB
- references/secrets-lockbox.md 4.6 KB
- references/serverless.md 5.1 KB
- references/vpc-network.md 4.0 KB
- references/yc-cli.md 3.8 KB
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 · 168 lines · 405 tokens per session scan A 0a57de39d957
yandex-cloud is a skill published in the GitHub repository VKirill/claude-lane-stack (115 stars, last pushed today), licensed MIT. It adds 405 tokens to every session and 3,123 once invoked, about $0.0020 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-05.
Other skills, from other repositories
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
deploy
Deploy an application to a configured environment.
coolify
Use when self-hosting apps and databases with Coolify on a VPS you own — install, first-admin lockdown, Git-to-deploy (Nixpacks/Dockerfile/compose), managed Postgres/Redis, scheduled S3 backups, domains + auto-SSL. NOT a PaaS someone else runs (that is railway), NOT sizing/hardening the box (that is hetzner), NOT…