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 aws-deployment-hotfix-operatorgit 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/aws-deployment-hotfix-operator)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/aws-deployment-hotfix-operator"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/aws-deployment-hotfix-operator/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/aws-deployment-hotfix-operator"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/aws-deployment-hotfix-operator.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.00598 |
| Opus 5 | $0.00028 | $0.00299 |
| Sonnet 5 | $0.00011 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
aws-deployment-hotfix-operator 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 7d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Deployment Hotfix Operator
Purpose
Act as the AWS deployment hotfix operator who makes the smallest safe repo change needed to unblock a deployment without pretending file edits are the same as production execution.
When to use
Use this skill for:
- rapid correction of deployment manifests, release parameters, config flags, or environment wiring in AWS-focused repos
- small deployment hotfixes that must stay in repo scope and avoid live-cloud mutation
- pre-deploy fixes where rollback notes, diff clarity, and validation matter more than speed theater
Lean operating rules
- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in
references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - This role has repo write access for bounded corrections, but it is non-destructive toward live AWS state by default. It may edit files and run validators; it must not apply, deploy, destroy, scale, rotate, or mutate live resources unless the user explicitly asks and a separate approval gate is satisfied.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, hidden blast radius, unsafe hotfixes, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full patch workflow, validation guidance, or formatting the final answer.
- Safety checklist — use before privileged, production-impacting, or rollback-sensitive recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- Deployment Hotfix Safety Guide — use for domain-specific failure modes, safe patch workflow, verification targets, and pushback criteria.
What ships with it
5 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.
- 7d ago First seen · 53 lines · 55 tokens per session scan A 37651cf66268
aws-deployment-hotfix-operator is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 55 tokens to every session and 598 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-09-04.
Other skills, from other repositories
usethis
R usethis package for workflow automation. Use for package setup, Git, GitHub, and project configuration.
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
bitbucket
Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines.
azure-deploy
WORKFLOW SKILL — Execute Azure deployments (azd up, azd deploy, terraform apply) for already-prepared apps with built-in error recovery. WHEN: 'run azd up', 'run azd deploy', 'push to production', 'go live', 'bicep deploy', 'terraform apply', 'publish to Azure'. DO NOT USE FOR: creating new apps (azure-prepare)…
gha-pr-merge-ref-shows-upstream-changes
Diagnose "my CI failed on a file I didn't change — the test passes locally but CI insists there's a duplicate / conflict / lint violation that isn't in my branch." Caused by GitHub Actions checking out refs/pull/N/merge (the auto-computed merge of PR head + base) on pullrequest events. Use when: (1) CI fails on a…
merge-queue-thrash-stop-inflow-and-open-prs-as-drafts
When main moves faster than the slowest CI leg, every open branch goes stale before it can merge and the whole queue jams with nothing red. Use when: (1) several PRs sit at mergeStateStatus BEHIND with auto-merge armed and none of them lands; (2) branches are being updated, re-running CI and going stale again before…