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 agentmods add skills/hiepdnh/agentic-development-lifecycle/ops-deploynpx skills add hiepdnh/Agentic-Development-Lifecycle --skill ops-deploygit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWrote 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/hiepdnh/agentic-development-lifecycle/ops-deploy)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/ops-deploy"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/ops-deploy.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.01075 |
| Opus 5 | $0.00032 | $0.00537 |
| Sonnet 5 | $0.00013 | $0.00215 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
ops-deploy 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 4d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /ops-deploy
Role: DevOps / Developer
Mục đích: Checklist và hướng dẫn deployment, đảm bảo không bỏ sót bước quan trọng.
Hướng dẫn thực hiện
Bước 1 — Gate: Thu thập thông tin deployment
## Tôi sẽ tạo deployment checklist.
Cho tôi biết:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Deploy lên môi trường nào? | A: Staging / B: Production / C: DR / D: Khác: ___ |
| 2 | Có database migration không? | A: Có / B: Không / C: Khác: ___ |
| 3 | Có config/env var thay đổi không? | A: Có — vars: ___ / B: Không / C: Khác: ___ |
| 4 | Có service dependency nào thay đổi? | A: Có — service: ___ / B: Không / C: Khác: ___ |
| 5 | Deployment window? | _(điền thời gian — có maintenance window không?)_ |
| 6 | Rollback plan nếu xảy ra sự cố? | _(mô tả)_ |
CI Quality Gate (phải pass trước khi deploy)
- [ ] Lint / format check
- [ ] Type check
- [ ] Unit tests pass
- [ ] Build thành công
- [ ] Integration tests pass
- [ ] Security scan: không có Critical/High CVE mới
Ask First: Nếu bất kỳ check nào fail → không deploy. Phải fix trước.
Bước 2 — Tạo Deployment Checklist
# Deployment Checklist: [Release version/feature]
**Date**: [Date]
**Environment**: [Staging/Production]
**Deploy by**: [Name]
**Reviewer**: [Name]
---
## Pre-deployment
### Code & Build
- [ ] PR đã được merge và CI pass
- [ ] Build artifact đã được verify trên Staging
- [ ] Version tag đã được tạo: `v[X.Y.Z]`
### Database
- [ ] Migration scripts đã được review
- [ ] Migration đã chạy thành công trên Staging
- [ ] Backup database production trước khi deploy
- [ ] Migration có rollback script chưa?
### Configuration
- [ ] Env vars mới đã được add vào production config
- [ ] Secret/credential đã được update (nếu có)
- [ ] Feature flags đã được set đúng
### Dependencies
- [ ] Service dependencies đã được notify (nếu breaking change)
- [ ] Third-party API quota đã được check
- [ ] Infrastructure đã scale up nếu cần
### Communication
- [ ] Stakeholder đã được thông báo về deployment
- [ ] Maintenance window đã được announce (nếu cần)
- [ ] On-call engineer đã sẵn sàng
---
## Deployment Steps
1. [ ] [Bước 1 — cụ thể theo project]
2. [ ] [Bước 2]
3. [ ] Verify health check endpoint
4. [ ] Monitor error rate 5 phút sau deploy
---
## Post-deployment Verification
- [ ] Smoke test: [Test case quan trọng nhất]
- [ ] API health check pass
- [ ] Error rate < [threshold]%
- [ ] Response time < [X]ms
- [ ] Logs không có ERROR unexpected
---
## Rollback Plan
**Trigger rollback khi**: [Điều kiện cụ thể]
**Bước rollback**:
1. [Bước rollback 1]
2. [Bước rollback 2]
**Ước tính thời gian rollback**: [X phút]
---
## Sign-off
- [ ] Deploy engineer: [Name] — [Time]
- [ ] QA verify: [Name] — [Time]
What ships with it
2 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.
- 4d ago First seen · 143 lines · 64 tokens per session scan A 64975893c415
ops-deploy is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 1,075 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…