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 VincentChuWaiChow/vanguard-frontier-agentic --skill alibaba-live-ack-rollout-guardgit clone --depth 1 https://github.com/VincentChuWaiChow/vanguard-frontier-agenticWrote 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/vincentchuwaichow/vanguard-frontier-agentic/alibaba-live-ack-rollout-guard)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/alibaba-live-ack-rollout-guard"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/alibaba-live-ack-rollout-guard/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/vincentchuwaichow/vanguard-frontier-agentic/alibaba-live-ack-rollout-guard"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/alibaba-live-ack-rollout-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01279 |
| Opus 5 | $0.00028 | $0.00639 |
| Sonnet 5 | $0.00011 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
alibaba-live-ack-rollout-guard 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 12d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alibaba Cloud Live ACK Rollout Guard
Purpose
Act as the guarded live Alibaba Cloud operator for alibaba-live-ack-rollout-guard work. Gate ACK deployment mutations, node pool scaling, and cluster version upgrades. Insist on PDB audit and rollback posture evidence before execution, and treat any ambiguous approval or target as a stop condition.
When to Use
Use this skill when:
- An ACK cluster version upgrade is requested (Kubernetes minor or patch version bump)
- A node pool is being scaled up or down (especially when removing nodes)
- A Deployment or DaemonSet rollout is being executed against a production workload
- Node pool configuration changes are planned (instance type, image version, count)
- An operator needs to audit PodDisruptionBudgets before a disruptive node pool operation
- An emergency rollback of a broken rollout is required
When NOT to Use
Do not use this skill when:
- The target is a non-production cluster with no PDB requirements and no live traffic
- The task is creating a brand-new cluster (no existing workloads at risk)
- The task is purely read-only cluster inspection with no mutation intent
- The task involves Function Compute, SAE, or other non-ACK compute
Cluster Type Awareness
ACK supports three cluster types — mutation procedures differ per type:
- Managed cluster: Control plane managed by Alibaba Cloud. Node pool upgrades and scaling are the primary mutation surface.
- Dedicated cluster: Full control plane access. Both control plane and data plane versions must be managed.
- Serverless cluster (ASK): No node pool concept. Pod-level scaling only — ECI instances are provisioned on demand. Version upgrades are less common but follow the same approval gate.
Always confirm cluster type before recommending a mutation path.
Pre-Flight Checklist
Before executing any ACK mutation, verify all of the following:
- Cluster identity confirmed — query the ACK API or Alibaba Cloud console to confirm the cluster ID, name, type, and region match the intended target.
- Active RAM principal confirmed — confirm the active identity has the required RAM policy (
AliyunCSFullAccessscoped to target cluster) for the operation. - Current cluster version and node pool version captured — document both before proceeding; confirm the target version is available for the cluster type.
- PDB audit complete — run
kubectl get pdb --all-namespacesand confirm no PDB hasDISRUPTIONS ALLOWED: 0for workloads running on the affected node pool. - Node drain posture verified — for scale-in operations, confirm all nodes to be removed can be safely drained (no pods with no toleration for eviction, no local storage).
- Rollback posture acknowledged — cluster version upgrades cannot be downgraded; operator must explicitly acknowledge this is one-way.
- Maintenance window confirmed — confirm the upgrade is within the approved change window.
- Rollout history captured — run
kubectl rollout history deployment/<NAME> -n <NAMESPACE>to document the pre-change state for Deployment rollouts.
What ships with it
3 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.
- 12d ago First seen · 103 lines · 55 tokens per session scan A d24d15a25174
alibaba-live-ack-rollout-guard is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 1,279 once invoked, about $0.0003 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
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
analyzing-azure-activity-logs-for-threats
Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity or…
implementing-azure-defender-for-cloud
Implementing Microsoft Defender for Cloud to enable cloud security posture management, workload protection across VMs, containers, databases, and storage, configure security recommendations, and set up adaptive security controls with automated remediation.
detecting-misconfigured-azure-storage
Detecting misconfigured Azure Storage accounts including publicly accessible blob containers, missing encryption settings, overly permissive SAS tokens, disabled logging, and network access violations using Azure CLI, PowerShell, and Microsoft Defender for Storage.
detecting-azure-lateral-movement
Detect lateral movement in Azure AD/Entra ID environments using Microsoft Graph API audit logs, Azure Sentinel KQL hunting queries, and sign-in anomaly correlation to identify privilege escalation, token theft, and cross-tenant pivoting.
subdomain-takeover-hunt
Detect and verify subdomain takeover via dangling CNAME to unclaimed services.