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/lync-cyber/cataforge/deploy-confignpx skills add lync-cyber/CataForge --skill deploy-configgit clone --depth 1 https://github.com/lync-cyber/CataForgeWrote 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/lync-cyber/cataforge/deploy-config)<a href="https://agentmods.dev/skills/lync-cyber/cataforge/deploy-config"><img src="https://agentmods.dev/badge/skills/lync-cyber/cataforge/deploy-config.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.00067 | $0.02191 |
| Opus 5 | $0.00034 | $0.01095 |
| Sonnet 5 | $0.00013 | $0.00438 |
| Haiku 4.5 | $0.00007 | $0.00219 |
Grade A, and why
deploy-config 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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
部署配置 (deploy-config)
能力边界
- 能做: CI/CD流水线配置、构建脚本编写、自动化测试集成、部署配置、容器化配置(Dockerfile/docker-compose)、环境配置管理、基础设施即代码(IaC)
- 不做: 源代码修改、测试编写、架构变更、CataForge 框架自身 CI/release 流水线（由仓库 .github/workflows 与 maintainer 维护）
输入规范
- arch#§1.4技术栈
- arch#§6目录结构
- test-report测试配置(流水线阶段)
- deploy-spec环境配置(容器/IaC阶段)
输出规范
- CI/CD配置文件(如 .github/workflows/)
- 构建脚本
- 容器化文件(Dockerfile, docker-compose.yml)
- 环境配置文件(.env.dev/.env.staging/.env.prod)
- IaC配置(Terraform/K8s manifests, 如适用)
操作指令
语言细则: 根据
framework.jsonproject.languages，按需载入本 skillreferences/lang-<lang>.md（仅 active 语言，逐个 Read），获取对应语言的构建部署细则（构建/打包工具、依赖锁定、CI 缓存策略、容器基镜像、产物发布）。
指令1: CI/CD流水线 (pipeline)
Step 1: 平台选型
根据arch#§1.4技术栈决定CI/CD平台:
- GitHub Actions(默认): 项目托管在GitHub时
- GitLab CI: 项目托管在GitLab时
- Jenkins: 企业内部部署、复杂流水线需求时
- 不确定时通过context查阅arch#§1.4技术栈决策，信息不足则标注[ASSUMPTION]
Step 2: 配置标准流水线阶段
按以下顺序配置流水线:
lint → unit-test → integration-test → build → deploy-staging → e2e-test → deploy-prod
- 每个阶段定义明确的成功/失败条件
- 阶段间设置依赖(前序失败则阻断后续)
- PR触发: lint + unit-test + integration-test
- 主分支合并: 完整流水线
Step 3: 集成自动化测试
- 单元测试: 每次push触发
- 集成测试: PR和主分支触发
- E2E测试: 部署到staging后触发
- 覆盖率报告: 集成到PR检查中
Step 4: 环境变量与密钥管理
- secrets 注入见 §密钥管理规范
- 环境差异通过环境变量控制(dev/staging/prod)
Step 5: 缓存策略
- 依赖缓存: 包管理器的依赖目录 / 下载缓存（按技术栈）
- 构建缓存: Docker layer cache / 编译产物缓存
- 缓存key包含lock文件hash，确保依赖变更时刷新
Step 6: 发布检查清单
- 版本号: 项目版本元数据与 Git tag 一致
- changelog: 已更新且包含当前版本条目
- 构建产物: 存档到artifact存储
- 通知: 部署结果通知(Slack/邮件/webhook)
指令2: 容器化配置 (container)
Step 1: Dockerfile编写
遵循最佳实践:
- 多阶段构建: 分离构建环境和运行环境，减小镜像体积
- 最小基础镜像: 优先使用alpine/slim/distroless变体
- 非root用户: 创建专用用户运行应用
- .dockerignore: 排除node_modules、.git、测试文件等
- 层缓存优化: 依赖安装层在代码复制层之前
- 健康检查: 定义HEALTHCHECK指令
Step 2: docker-compose编排
- 服务定义: 每个服务指定image/build、ports、volumes、depends_on
- 网络: 定义服务间通信网络(前端/后端/数据库分离)
- 卷: 数据持久化卷(数据库) + 开发时代码热重载卷
- 健康检查: 依赖服务设置healthcheck，使用depends_on.condition: service_healthy
- compose profiles: 通过profiles区分dev/test/prod服务组合
What ships with it
6 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.
- 5d ago First seen · 159 lines · 67 tokens per session scan A 2402cba1980d
deploy-config is a skill published in the GitHub repository lync-cyber/CataForge (128 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 2,191 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
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
konflux-build
Create a manual Konflux build from a PR with configurable image expiry (default 30 days).
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.