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 Qovery/qovery-skills --skill qovery-deploygit clone --depth 1 https://github.com/Qovery/qovery-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/qovery/qovery-skills/qovery-deploy)<a href="https://agentmods.dev/skills/qovery/qovery-skills/qovery-deploy"><img src="https://agentmods.dev/badge/skills/qovery/qovery-skills/qovery-deploy.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.1 | $0.00138 | $0.03482 |
| Opus 5 | $0.00069 | $0.01741 |
| Sonnet 5 | $0.00028 | $0.00696 |
| Haiku 4.5 | $0.00014 | $0.00348 |
Grade A, and why
qovery-deploy 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 4d 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.
QOVERY_ORG_ID=$(curl -s -H "Authorization: Token $QOVERY_API_TOKEN" -H "User-Agent: $QOVERY_SKILLS_UA" \ The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
16 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.
- commands/qovery-deploy.md 874 B
- examples/fullstack.md 7.6 KB
- reference/auth.md 4.7 KB
- reference/console-url-detection.md 2.4 KB
- reference/phase1-discovery.md 8.4 KB
- reference/phase10-troubleshooting.md 14 KB
- reference/phase2-prereq-auth.md 4.2 KB
- reference/phase2b-cluster-setup.md 11 KB
- reference/phase3-dockerfiles.md 8.9 KB
- reference/phase3b-deployment-plan.md 4.7 KB
- reference/phase3c-blueprints.md 13 KB
- reference/phase4-cli-api.md 12 KB
- reference/phase5-terraform.md 19 KB
- reference/phase6-env-vars.md 17 KB
- reference/phase8-advanced-patterns.md 6.2 KB
- reference/phase9-watching.md 5.6 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.
- 4d ago Changed · +6 lines ff9e73060bef
- 8d ago First seen · 219 lines · 138 tokens per session scan A 5d2fbe540155
qovery-deploy is a skill published in the GitHub repository Qovery/qovery-skills (11 stars, last pushed 6d ago), with no licence file. It adds 138 tokens to every session and 3,482 once invoked, about $0.0007 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-31.
Other skills, from other repositories
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
k8s-autoscaling
Configure Kubernetes autoscaling with HPA, VPA, and KEDA. Use for horizontal/vertical pod autoscaling, event-driven scaling, and capacity management.
k8s-capi
Cluster API lifecycle management for provisioning, scaling, and upgrading Kubernetes clusters. Use when managing cluster infrastructure or multi-cluster operations.
k8s-deploy
Deploy and manage Kubernetes workloads with progressive delivery. Use for deployments, rollouts, blue-green, canary releases, scaling, and release management.
k8s-multicluster
Manage multiple Kubernetes clusters, switch contexts, and perform cross-cluster operations. Use when working with multiple clusters, comparing environments, or managing cluster lifecycle.
k8s-backup
Kubernetes backup and restore with Velero. Use when creating backups, restoring applications, managing disaster recovery, or migrating workloads between clusters.