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/gaelic-ghost/socket/cloud-deployment-routing-workflownpx skills add gaelic-ghost/socket --skill cloud-deployment-routing-workflowgit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/cloud-deployment-routing-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/cloud-deployment-routing-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/cloud-deployment-routing-workflow.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.00043 | $0.01832 |
| Opus 5 | $0.00022 | $0.00916 |
| Sonnet 5 | $0.00009 | $0.00366 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
cloud-deployment-routing-workflow 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 yesterday.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Deployment Routing Workflow
Purpose
Choose the smallest correct cloud deployment path before changing infrastructure, credentials, or production-facing configuration.
The practical decision is whether the agent should use an official provider plugin, a provider MCP server, a provider CLI, a framework-owned deployment workflow, or a Socket-owned provider skill.
When To Use
- Use this skill when the user wants cloud deployment help and has not chosen a provider-owned workflow.
- Use this skill when a project mentions AWS, Cloudflare, Vercel, Fly.io, Azure, GCP, Terraform, Pulumi, CDK, CloudFormation, SAM, containers, serverless, hosting, DNS, secrets, deployment, or production infrastructure.
- Use this skill before adding provider credentials, changing cloud resources, deploying production services, or wiring new MCP server configuration.
- Use this skill when an official provider plugin may already own the requested work.
Source Check
Use repo-local deployment files, checked-out provider config, installed provider CLIs, official provider plugins, and official provider documentation before making claims about current deployment behavior:
- Agent Toolkit for AWS
- AWS Agent Toolkit plugins
- AWS MCP Server setup
- AWS CLI
- AWS SAM CLI
- Azure Skills
- Azure MCP Server
- Azure Developer CLI
Translate any documentation rule into the concrete repository decision it changes.
Routing Workflow
- Inspect the project shape:
- deployment manifests such as
template.yaml,serverless.yml,cloudformation.yml,cdk.json,samconfig.toml,wrangler.toml,vercel.json,fly.toml,Dockerfile,compose.yaml, Terraform, or Pulumi files - package scripts, Make targets, CI workflows, release docs, and provider-specific README sections
- existing credentials guidance, environment variables, account aliases, regions, profiles, and secret names
- deployment manifests such as
- Identify the deployment job:
- provider selection
- local credential setup
- documentation lookup
- infrastructure planning
- preview or diff
- dev/staging deploy
- production deploy
- failure triage
- cost, IAM, observability, or rollback review
- Route AWS work first:
- Prefer the official AWS Agent Toolkit for AWS for Codex when the task is general AWS discovery, AWS MCP access, AWS CLI or AWS SAM setup, CDK, CloudFormation, serverless, containers, storage, observability, billing, SDK usage, or deployment.
- Install path for Codex users:
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.
- yesterday First seen · 142 lines · 43 tokens per session scan A 7f4a74e82821
cloud-deployment-routing-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,832 once invoked, about $0.0002 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-03.
Other skills, from other repositories
b2-cloud-storage
Manage Backblaze B2 cloud storage. List files, audit usage, estimate cost, clean up stale data, review security posture, and manage lifecycle rules. Use when the user mentions B2, Backblaze, object storage buckets, or storage cleanup.
blob-store
This skill should be used when the user wants a "blob store" or "object storage", names "S3" or an S3-compatible store, needs to "store images / video / files", asks about "multipart upload" or "resumable upload", "signed / presigned URLs", "media storage", "unstructured data at scale", object "versioning", storage…
dns
This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and…
pipeline
Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…
web-infra-plan
Produce a sprint INFRA.md covering Terraform / gcloud changes — dry-run plan, IAM diff, cost estimate, rollback. Coordinator-only — does not apply infra changes. Pauses for user confirmation. Bias toward GCP+Terraform but works with Pulumi / CloudFormation / Serverless / CDK.
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…