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 skills/rahmanef63/si-coder-agent/sc-convex-cloudnpx skills add rahmanef63/si-coder-agent --skill sc-convex-cloudgit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWrote 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/rahmanef63/si-coder-agent/sc-convex-cloud)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-convex-cloud"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-convex-cloud.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.00082 | $0.01478 |
| Opus 5 | $0.00041 | $0.00739 |
| Sonnet 5 | $0.00016 | $0.00296 |
| Haiku 4.5 | $0.00008 | $0.00148 |
Grade A, and why
sc-convex-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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc-convex-cloud — Convex Cloud (managed)
Use this skill when the user wants to deploy, debug, or maintain a Convex Cloud (managed) backend — the online-path counterpart to /sc-convex (self-hosted on Dokploy). The repo lives at https://github.com/rahmanef63/si-coder-agent.
flowchart LR
A["/sc-convex-cloud"] --> B["scripts/deploy-cloud.js<br/>CONVEX_DEPLOY_KEY (env, never echoed)"]
B --> C["npx convex deploy<br/>→ Convex Cloud"]
C --> D["inject NEXT_PUBLIC_CONVEX_URL<br/>into the build"]
D --> E["probe /version (*.convex.cloud)<br/>+ JWKS (*.convex.site)"]
E --> F["ready ✅"]
NEVER ask the user to run Convex CLI by hand
All Convex Cloud deploys go through scripts/deploy-cloud.js. Do not instruct the user to run npx convex deploy interactively, nor to hand-set NEXT_PUBLIC_CONVEX_URL. The deploy key is passed via the script's env and never echoed. If a deploy fails, debug it with scripts/check-cloud.js and fix root cause — do not punt the Convex CLI call to the user.
Pre-requisites
CONVEX_DEPLOY_KEY— production (or preview) deploy key for the Cloud deployment. Required.CONVEX_DEPLOYMENT— optional local-dev marker written bynpx convex dev. NOT used in CI.
If CONVEX_DEPLOY_KEY is missing, route the user to /sc-onboarding.
CORE MANDATES (LEARNED LESSONS)
- Coupled build is the source of truth for the URL: let
npx convex deploy --cmd '<build>'injectNEXT_PUBLIC_CONVEX_URLat build time. Never hardcode the URL in two places — the--cmdinjection wins. - Next.js needs the
NEXT_PUBLIC_prefix override: the default injected var isCONVEX_URL, which never reaches the browser. ALWAYS pass--cmd-url-env-var-name NEXT_PUBLIC_CONVEX_URL. - Deploy key is a secret: never log/echo it. Pass it via the process
env, never interpolate it into a shell command string. - Set
CONVEX_DEPLOY_KEYonly on the matching env: a prod key → Production only; a preview key → Preview only. Never setCONVEX_DEPLOYMENTin CI. - Project + key creation is human-one-time: there is no anonymous Cloud-project create API. Mint keys headlessly only after a first interactive login (
npx convex deployment token create <name> --prod --save-env).
What ships with it
2 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.
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 · 80 lines · 82 tokens per session scan A ecfc6f2880ef
sc-convex-cloud is a skill published in the GitHub repository rahmanef63/si-coder-agent (14 stars, last pushed 7d ago), licensed MIT. It adds 82 tokens to every session and 1,478 once invoked, about $0.0004 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-30.
Other skills, from other repositories
convex-self-hosting
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other…
setup-convex-worktrees
Set up, repair, or explain isolated Convex development deployments for Git worktrees and coding agents, including per-worktree env bindings, temporary deployment creation, baseline data seeding, frontend port isolation, and AGENTS.md guardrails. Use when separate checkouts are clobbering one shared Convex dev…
garage
Operate Joel's Garage S3-compatible object storage on three-body. Use for Garage, Convex Garage, Garage S3, three-body Garage, port 39100, Garage buckets, and MinIO-to-Garage migration.
deployhq
Deploy code, manage servers, and automate infrastructure via the DeployHQ CLI (dhq). Use when the user wants to deploy, check deployment status, manage projects/servers, or interact with the DeployHQ platform.
Convex Cron Jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks.
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…