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 commands/qovery/qovery-skills/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/commands/qovery/qovery-skills/qovery-deploy)<a href="https://agentmods.dev/commands/qovery/qovery-skills/qovery-deploy"><img src="https://agentmods.dev/badge/commands/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 | $0.00009 | $0.00194 |
| Opus 5 | $0.00005 | $0.00097 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
qovery-deploy 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.
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 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 · 17 lines · 9 tokens per session scan A f5d48cf17c95
qovery-deploy is a command published in the GitHub repository Qovery/qovery-skills (11 stars, last pushed 3d ago), with no licence file. It adds 9 tokens to every session and 194 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
deploy
You are tasked with deploying the mcp-server-langgraph application to various targets. This command.
sealos
Deploy projects to Sealos Cloud, prepare Docker artifacts, convert Compose files, assess cloud readiness, build Sealos Desktop apps, connect databases, or use Sealos S3 object storage.
deploy
Build, test, deploy with staged rollout.
k8s-manifest
Generate production-ready Kubernetes manifests for the current application.
extract-infrastructure
Extract Azure infrastructure and generate Docker Compose stack for local development.
gen-infra
Generate Infrastructure as Code: Docker Compose, Kubernetes manifests, K3s manifests, Terraform configs, or Helm charts. Usage: /gen-infra [docker|k8s|k3s|terraform|helm] [--env=production].