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 oomol-lab/skills --skill oo-aliyun-ossgit clone --depth 1 https://github.com/oomol-lab/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/skills/oomol-lab/skills/oo-aliyun-oss)<a href="https://agentmods.dev/skills/oomol-lab/skills/oo-aliyun-oss"><img src="https://agentmods.dev/badge/skills/oomol-lab/skills/oo-aliyun-oss/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/oomol-lab/skills/oo-aliyun-oss"><img src="https://agentmods.dev/badge/skills/oomol-lab/skills/oo-aliyun-oss.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.00056 | $0.00980 |
| Opus 5.5 | $0.00022 | $0.00392 |
| Sonnet 5.5 | $0.00011 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade C, and why
oo-aliyun-oss scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux This is a copy
75% identical to oo-17track — 41 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alibaba Cloud OSS
Operate Alibaba Cloud OSS through your OOMOL-connected account. This skill calls the aliyun_oss connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.
Running an action
Assume the user has already installed the oo CLI, signed in, and connected Alibaba Cloud OSS. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.
1. Inspect the contract to get the authoritative input/output schema before building a payload:
oo connector schema "aliyun_oss" --action "<action_name>"
2. Run the action with a JSON payload that matches the input schema:
oo connector run "aliyun_oss" --action "<action_name>" --data '<json>' --json
--datatakes a JSON object string or@path/to/file.json; omit it to send{}.- The response is
{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives undermeta.executionId.
Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.
Available actions
delete_object— Delete one OSS object. [destructive]download_object— Download one OSS object into connector transit storage.generate_presigned_url— Generate a pre-signed OSS URL for reading, uploading, or deleting one object.head_object— Fetch structured metadata for one OSS object.list_buckets— List OSS buckets visible to the connected Alibaba Cloud credential.list_objects— List objects in an OSS bucket with the ListObjectsV2 API.put_object— Upload one object to OSS from a public URL, plain text, or base64-encoded content. [destructive]
Safety
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 Changed 571e7e4b8ad7
- 1mo ago Changed fcf8e2912b44
- 1mo ago Changed · -1 lines 9e21d57a85c2
- 1mo ago Changed · +1 lines 813606b0bae8
- 1mo ago First seen · 85 lines · 56 tokens per session scan C d2c49485e465
oo-aliyun-oss is a skill published in the GitHub repository oomol-lab/skills (2 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 980 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 75% identical to oo-17track, differing in 41 lines, and is treated as a copy.
Other skills, from other repositories
docker-deploy
Use this skill when writing or reviewing a Dockerfile, docker-compose setup, or container image build for a project, or when debugging a container that won't build, start, or stay healthy. Triggers: user says "docker", "Dockerfile", "container", "image", "docker compose", "containerize", "multi-stage", "distroless"…
backup-recovery
Design and verify backups and restoration for owned databases, files and application state. Use when preparing recovery, migrating data or testing backups; protect the source and prove restore into an isolated destination before calling recovery ready.
cloud-architecture
Choose and design cloud services from concrete application, data, availability and operational requirements. Use when comparing AWS, Azure, GCP, Cloudflare or VPS architectures; preserve provider/account constraints and verify region-specific capabilities.
infrastructure-as-code
Build and maintain Terraform, OpenTofu, Pulumi or cloud-native IaC with reviewable plans and protected state. Use when provisioning owned resources or fixing drift; preserve the project chosen engine, backend and provider contracts.
kubernetes-operations
Operate and deploy owned Kubernetes workloads with explicit cluster, namespace and rollout identity. Use when configuring Deployments, Services, probes, resources or diagnosing a known workload; do not expand an application task into uncontrolled cluster administration.
remote-debugging
Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence. Use when local behavior differs from a known server or deployment; start read-only and keep diagnosis separate from disruptive remediation.