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 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/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/gaelic-ghost/socket/cloud-deployment-routing-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/cloud-deployment-routing-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01832 |
| Opus 5.5 | $0.00017 | $0.00733 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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 1mo 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.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
cloud-administration
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get…
network-administration
Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
virtualization-operations
Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a cluster, work out why VMs are slow when the hosts look idle, clean up sprawl, set…
systems-administration
Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have…
business-continuity-and-resilience
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.