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 xiaohei-info/oh-my-multica --skill software-design-lifecycle-deploy-ops-methodologygit clone --depth 1 https://github.com/xiaohei-info/oh-my-multicaWrote 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/xiaohei-info/oh-my-multica/software-design-lifecycle-deploy-ops-methodology)<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-deploy-ops-methodology"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-deploy-ops-methodology/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/xiaohei-info/oh-my-multica/software-design-lifecycle-deploy-ops-methodology"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-deploy-ops-methodology.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.00058 | $0.00636 |
| Opus 5 | $0.00029 | $0.00318 |
| Sonnet 5 | $0.00012 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
software-design-lifecycle-deploy-ops-methodology 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 11d 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.
What it actually says
Deploy / Ops Methodology
Overview
This is the architect profile's 部署运维阶段方法论 skill.
When to Use
Use when:
- 概要设计与详细设计已 review 确认
- the architect must hand design into deployment and operational reality
Canonical Stage Doctrine (Full Preservation)
四、部署运维
时间：概要设计文档、详细设计文档等在技术人员review确认后（前后端rd、数据rd、qa、pm）
输入：概要设计文档、详细设计文档
输出：部署运维文档
过程：
| 步骤 | 问题 | 答案 |
|---|---|---|
| 物理架构 | 硬件与网络拓扑 | 部署架构图 |
| 部署方案 | 是否支持分批发布、灰度发布、金丝雀发布？上线顺序、验证步骤、回滚入口是什么？ | 上线方案 / SOP |
| 运维手册 | 运维步骤、运维工具、运维措施、故障处理 SOP | |
| 监控与告警 | 核心监控指标、告警阈值、通知方式、值班人与升级路径是什么？ | 监控告警清单 |
| 应急预案 | 出现故障后如何止血、回滚、扩容、降级、切流、恢复与核对？ | 应急预案 |
| 容量与演练 | 是否有容量评估、压测方案、容灾演练、回滚演练？ | 演练记录 / 计划 |
Architect Execution Layer
- do not hand off a design whose runtime assumptions are still implicit
- make rollback, degrade, recovery, and rehearsal paths explicit
- ensure ownership and operational boundaries are clear
- treat monitoring and emergency handling as first-class outputs
Companion Diagram / Artifact Skills
arch-lifecycle-deploy-ops-deployment-arch-diagramming
Verification Checklist
- Physical topology / deployment shape is explicit
- Rollout and rollback expectations are explicit
- Monitoring / alerting / emergency assumptions are explicit
- Capacity and rehearsal expectations are explicit
- Design handoff is operationally actionable
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.
- 11d ago First seen · 65 lines · 58 tokens per session scan A 7f9f33007e8b
software-design-lifecycle-deploy-ops-methodology is a skill published in the GitHub repository xiaohei-info/oh-my-multica (26 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 636 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
multi-service-orchestration
PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.
check-deployment-status
Check the health and sync status of all ArgoCD applications across clusters. Identifies out-of-sync, degraded, or unhealthy deployments and provides actionable remediation steps. Use when monitoring deployments, troubleshooting sync failures, or verifying environment health after a release.
cluster-resource-health
Check Kubernetes cluster health including pod status, node conditions, resource utilization, and pending alerts across EKS clusters. Use when monitoring infrastructure health, investigating capacity issues, or performing cluster audits.
aws-essentials
Use when standing up the core AWS surface a small product needs: hardening a fresh account, a private S3 bucket, encrypted RDS Postgres, ECS Fargate vs EC2, CloudFront + OAC, or scoping an IAM policy to least privilege. NOT the CI pipeline that ships the container (that is deployment), NOT app-code access-control…
fly-io
Use when deploying or operating an app on Fly.io — writing fly.toml, placing Machines in regions near users, attaching Volumes, managing secrets, or picking a scaling lever (autostop/autostart, scale count, fly-replay). NOT choosing which host to deploy on (that is deployment), NOT a git-push PaaS with no regions…
netlify
Use when deploying or operating a site on Netlify — writing or fixing netlify.toml, authoring Functions or Edge Functions, redirects, rewrites and headers, env vars per deploy context, and shipping via the Netlify CLI. NOT deploying to Vercel (that is vercel).