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 linshidream/skill-hub --skill ci-triggergit clone --depth 1 https://github.com/linshidream/skill-hubWrote 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/linshidream/skill-hub/ci-trigger)<a href="https://agentmods.dev/skills/linshidream/skill-hub/ci-trigger"><img src="https://agentmods.dev/badge/skills/linshidream/skill-hub/ci-trigger/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/linshidream/skill-hub/ci-trigger"><img src="https://agentmods.dev/badge/skills/linshidream/skill-hub/ci-trigger.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.02029 |
| Opus 5.5 | $0.00022 | $0.00812 |
| Sonnet 5.5 | $0.00011 | $0.00406 |
| Haiku 4.5 | $0.00006 | $0.00203 |
Grade A, and why
ci-trigger 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 1mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD 触发与监控
目标
当用户的代码已合并到测试分支,需要部署到测试环境时,使用本 skill 触发 Jenkins CI 构建、监控构建状态、等待较长 package 流程、拉取失败日志分析原因,并输出可继续处理的结构化报告。
V1 实现 Jenkins 和可选钉钉通知。GitHub Actions、GitLab CI、企业微信、飞书和 Slack 属于 V2,只有对应 adapter 实现后才能在元数据和 .dev-flow.yml schema 中声明为可用。
使用场景
当用户说出类似需求时触发:
- "触发构建"
- "部署到测试环境"
- "跑一下 Jenkins"
- "构建一下"
- "打包部署"
前置条件
- 项目根目录存在
.dev-flow.yml,且ci配置块已填写 - CI 系统的认证凭据已通过环境变量设置(如
JENKINS_URL、JENKINS_USER、JENKINS_TOKEN) - 代码已推送到目标分支
执行流程
阶段 1: 准备
- 读取
.dev-flow.yml的ci配置 - 验证必要环境变量已设置(检查是否非空,不读取值)
- 确定动态参数:
{{branch}}← 从活动状态文件(由 dev-lifecycleresolve-active-state.py解析路径,per-feature 模式下.dev-flow/states/<feature>.json)或当前 git branch 获取{{version}}← 从项目pom.xml/package.json/pyproject.toml解析
- 展示即将触发的构建参数
阶段 2: 触发
-
调用
scripts/trigger.sh,根据ci.system分发到对应适配脚本Jenkins:
bash scripts/trigger.sh --system jenkins --job your-project-pipeline \ --params "CURRENT_VERSION=v1.0.1&ACTIVE=test&GIT_BRANCH=feat/zx/xxx" -
获取构建编号 / Run ID
-
更新活动状态文件(路径由编排器通过
--state传入,或脚本默认.dev-flow-state.json兜底):phase=building,记录build.system、build.number、build.status
阶段 3: 监控
- 按
ci.{system}.poll.interval轮询构建状态 - package 或镜像构建较慢时继续等待,直到
ci.{system}.poll.timeout- 默认建议
timeout=1800秒,项目 package 更慢时可继续调大 - 每次轮询输出简短进度,不把长日志刷屏
- 默认建议
- 超过
timeout则超时报告,并保留 build number 供下次继续查询 - 每次轮询输出简短进度
阶段 4: 报告
- 构建成功:
- 输出部署信息(版本号、环境、耗时)
- 更新活动状态文件 phase 为
deployed-test - 如果
notify.enabled=true且配置了钉钉,调用scripts/notify-dingtalk.sh
- 构建失败:
- 立即拉取失败日志(
scripts/fetch-log.sh) - 分析失败原因:
- 编译失败 → 定位报错文件和行号
- 测试失败 → 列出失败的 test case
- package 失败 → 定位 Maven/Gradle/npm 打包阶段错误
- Docker 构建失败 → 检查 Dockerfile
- 网络/依赖问题 → 建议重试
- 输出分析结果
- 更新 state:
build.status=failure,phase 回到code:revising - 建议下一步操作:回到 code review/revising,修复后重新触发构建
- 如果
notify.enabled=true且配置了钉钉,发送失败通知
- 立即拉取失败日志(
凭据安全
所有凭据通过环境变量传递,脚本中使用 ${ENV_VAR} 引用:
What ships with it
11 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.
- adapters/claude-code.md 3.2 KB
- examples/jenkins-failure-log.txt 886 B
- examples/jenkins-success.md 876 B
- README.md 1.7 KB
- scripts/adapters/jenkins.sh 2.5 KB runs code
- scripts/dev-flow-util.py 6.1 KB runs code
- scripts/fetch-log.sh 3.2 KB runs code
- scripts/notify-dingtalk.sh 2.0 KB runs code
- scripts/poll-status.sh 4.5 KB runs code
- scripts/trigger.sh 5.6 KB runs code
- skill.json 743 B
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.
- 1mo ago First seen · 217 lines · 55 tokens per session scan A e7dbab035e54
ci-trigger is a skill published in the GitHub repository linshidream/skill-hub (20 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 2,029 once invoked, about $0.0002 per session on Opus 5.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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…