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 DeployGate/deploygate-agent-plugin --skill ci-setupgit clone --depth 1 https://github.com/DeployGate/deploygate-agent-pluginWrote 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/deploygate/deploygate-agent-plugin/ci-setup)<a href="https://agentmods.dev/skills/deploygate/deploygate-agent-plugin/ci-setup"><img src="https://agentmods.dev/badge/skills/deploygate/deploygate-agent-plugin/ci-setup/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/deploygate/deploygate-agent-plugin/ci-setup"><img src="https://agentmods.dev/badge/skills/deploygate/deploygate-agent-plugin/ci-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.01108 |
| Opus 5.5 | $0.00007 | $0.00443 |
| Sonnet 5.5 | $0.00004 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
ci-setup scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `references/external-ci.md` — CircleCI / Codemagic / curl-based integration. Read for anything other than GitHub Actions or Bitrise How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeployGate CI/CD Setup
Guide users through setting up CI/CD integration for automated app uploads and PR-based distribution.
When to use
When the user wants to:
- Automate DeployGate uploads from CI
- Set up PR-based distribution pages
- Integrate DeployGate with GitHub Actions, Bitrise, CircleCI, or other CI
Reference files
Load only what matches the detected CI provider and project type. Each file is substantial (full YAML templates) — do NOT preload.
references/github-actions-upload.md— GitHub Actions main-branch upload workflow template (full YAML with Android + iOS examples). Read when generating the main-branch workflowreferences/github-actions-pr.md— GitHub Actions PR distribution workflow template (full YAML with comment / deployment / cleanup logic). Read when generating the PR workflowreferences/ios-code-signing.md— iOS code signing setup for CI (fastlane match vs manual .p12 + ASC API key). Read when the project is iOSreferences/bitrise.md— Bitrise DeployGate upload step. Read for Bitrisereferences/external-ci.md— CircleCI / Codemagic / curl-based integration. Read for anything other than GitHub Actions or Bitrisereferences/troubleshooting.md— troubleshooting table. Read on error
Step 1: Detect CI Environment
Check the project for existing CI configuration:
.github/workflows/→ GitHub Actions (native integration available)bitrise.yml→ Bitrise (official DeployGate step available).circleci/config.yml→ CircleCI (curl-based upload)codemagic.yaml→ Codemagic (curl-based upload)- None found → Recommend GitHub Actions for new setup
Also detect the project type:
build.gradle/build.gradle.kts→ Android (runs on ubuntu-latest)*.xcodeproj/*.xcworkspace→ iOS (requires macos-latest runner)
Step 2: Configure Secrets
For CI, recommend using the project API key instead of a personal API key. Project API keys are not tied to a specific user, so CI won't break when team members leave or change roles.
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.
- 3d ago Changed 2615a80e34c7
- 1mo ago First seen · 113 lines · 18 tokens per session scan A 29f40c48a857
ci-setup is a skill published in the GitHub repository DeployGate/deploygate-agent-plugin (3 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 1,108 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
ci-workflow
Design and maintain .NET CI workflows for F#, C#, and mixed solutions with SDK setup, restore, build, test, format checks, package checks, caching, and matrix decisions.
diagnosing-ci-and-merge-bottlenecks
Diagnoses CI and pull-request pipeline health for a GitHub repo using the engineering analytics MCP tools — pull-requests (PR list with CI status), workflow-health (per-workflow CI trends), and pr-lifecycle (a single PR's timeline). Use when asked whether CI is getting faster or slower, which GitHub Actions workflow…
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.
scaffolding
Setting up a new project or package: scripts, test, lint, typecheck, CI, tooling. Load before creating files.
cicd
This skill should be used when the user mentions keywords related to cicd.