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 EthanYoQ/Skill-hub --skill aliyun-openapi-mcp-opsgit clone --depth 1 https://github.com/EthanYoQ/Skill-hubWrote 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/ethanyoq/skill-hub/aliyun-openapi-mcp-ops)<a href="https://agentmods.dev/skills/ethanyoq/skill-hub/aliyun-openapi-mcp-ops"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/aliyun-openapi-mcp-ops/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/ethanyoq/skill-hub/aliyun-openapi-mcp-ops"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/aliyun-openapi-mcp-ops.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.00000 | $0.01364 |
| Opus 5 | $0.00000 | $0.00682 |
| Sonnet 5 | $0.00000 | $0.00273 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
aliyun-openapi-mcp-ops 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 10d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Category: service
Alibaba Cloud OpenAPI MCP Ops
Use this skill when:
- Codex can see an Alibaba Cloud custom MCP server, but the required tools are missing.
- You need to close SWAS deployment permissions before bootstrap or release.
- You need to verify OAuth, tool loading, region, instance discovery, or Cloud Assistant readiness.
- You are using a project-integrated OpenAPI MCP server instead of an Aliyun plugin.
This skill is based on a verified SWAS deployment-prep workflow against a custom OpenAPI MCP server.
Scope
This skill covers:
- Custom OpenAPI MCP server endpoint and OAuth handling
- Selector updates for SWAS deployment operations
- Codex desktop reload behavior after MCP changes
- SWAS instance readiness checks before deployment
- Low-risk remote command validation through Cloud Assistant
This skill does not cover:
- Full application deployment steps
- Public web ingress setup
- ECS-specific operations outside the SWAS path
Core Lessons
-
A custom OpenAPI MCP server may authenticate successfully while still missing required tools. OAuth success does not imply deployment selectors are present.
-
The custom MCP server id in the endpoint path is case-sensitive. If the id casing is wrong, the browser flow may still open, but the server will not load correctly.
-
Codex desktop does not reliably hot-load newly added MCP servers or updated selector sets. After changing the MCP config or custom server selectors, restart Codex before concluding the tools are still missing.
-
Read-only SWAS selectors are not enough for deployment. For deployment preparation, you need remote execution capability.
-
For SWAS deployment, the minimal useful mutating selectors are:
RunCommandCreateCommandInvokeCommandDeleteCommandCreateSnapshot(recommended before first deploy)
-
Firewall write permissions are not required by default for this project. If the app uses Feishu long connection and does not need inbound public HTTP immediately, do not add firewall write selectors unless a real deployment step needs them.
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.
- 10d ago First seen · 162 lines · 0 tokens per session scan A 988730283042
aliyun-openapi-mcp-ops is a skill published in the GitHub repository EthanYoQ/Skill-hub (9 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,364 tokens. 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 skills, from other repositories
tcapi
A helper for managing Tencent Cloud resources through Tencent Cloud's command-line API tool. Tencent Cloud is a cloud-services provider offering products such as virtual servers, storage, networks, and containers.
atmos-migration
This skill helps you migrate a repository to Atmos. It covers native Terraform, Terraform Workspaces, Terramate, Terragrunt, Makefiles, Justfiles, and Taskfiles. It gives minimum-disruption paths, file-layout options, workspace mapping, task-to-command mapping, generatehcl/script decomposition, and the remote-state…
atmos-components
Component architecture: Terraform root modules, remote source provisioning, abstract components, component inheritance, versioning, mixins, catalog patterns.
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.
atmos-design-patterns
Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration.
atmos-kubernetes
Native Kubernetes components (experimental): render/plan/diff/apply/deploy/delete/validate via Kubernetes Go SDK server-side apply, components.kubernetes, kubectl/kustomize providers, paths/manifests, provision targets (cluster vs. GitOps repo), and auth.