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 deploygit 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/deploy)<a href="https://agentmods.dev/skills/deploygate/deploygate-agent-plugin/deploy"><img src="https://agentmods.dev/badge/skills/deploygate/deploygate-agent-plugin/deploy/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/deploy"><img src="https://agentmods.dev/badge/skills/deploygate/deploygate-agent-plugin/deploy.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.00014 | $0.00638 |
| Opus 5.5 | $0.00006 | $0.00255 |
| Sonnet 5.5 | $0.00003 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
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 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.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build and upload app to DeployGate
Build the current project and upload the binary to DeployGate. This is the fast-path skill — a quick build + upload for a project that is already set up. For first-time setup, iOS code signing issues, UDID registration, distribution page creation, or notification configuration, escalate to the setup skill instead.
When to escalate to the setup skill
Stop this skill and suggest the user invoke setup if any of these apply:
- The user has never uploaded to DeployGate before (no API token configured)
- iOS build fails with a code signing / provisioning profile error
- A tester reports they can't install the app (UDID registration needed)
- The user needs to create or configure a distribution page
- The user wants to configure notifications
The setup skill owns the full onboarding flow and its detailed references cover these paths.
Steps
-
Detect project type by checking for build files:
build.gradle/build.gradle.kts→ Android*.xcodeproj/*.xcworkspace→ iOS- If both exist, ask the user which platform to build
-
Get owner name using the
get_user_infoMCP tool -
Build the app:
- Android:
./gradlew assembleDebug→app/build/outputs/apk/debug/app-debug.apk - iOS: guide the user to build with
fastlane gymor Xcode Archive, then provide the IPA path - Do NOT use APKs from Android Studio's Instant Run / Apply Changes
- Android:
-
Collect Git info for the upload message:
git rev-parse --short HEAD # commit hash git rev-parse --abbrev-ref HEAD # branch nameFormat:
"{branch} ({hash})"— e.g."feature/login (abc1234)" -
Upload using the
upload_appMCP tool:owner_name: from step 2file_path: path to the built binarymessage: Git info from step 4- If the user specifies a distribution page, include
distribution_keyordistribution_name
-
Show results: display the upload response including the app URL and revision number
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 3dcef6eea829
- 1mo ago First seen · 57 lines · 14 tokens per session scan A 49695e442530
deploy is a skill published in the GitHub repository DeployGate/deploygate-agent-plugin (3 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 638 once invoked, about $0.0001 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-31.
Other skills, from other repositories
icon-composer-app-icon-workflow
Design, preview, validate, and integrate Apple app icons with Icon Composer. Use when a task mentions Icon Composer, .icon documents, Liquid Glass app icons, ictool preview exports, app icon design for iOS, iPadOS, macOS, or watchOS, or guided Icon Composer GUI work through Computer Use.
bootstrap-xcode-workspace
Create, adopt, extend, and align one Swift product workspace with app, extension, package, and service components under one permanent Xcode entrypoint.
build-kotlin-android
Implement Kotlin-first Android app or library changes, including activities, fragments, services, receivers, Compose UI, XML/AppCompat UI, AndroidX, lifecycle-aware coroutines, state, persistence touchpoints, resources, accessibility labels, navigation touchpoints, tests, lint, and validation while preserving repo…
gradle-agp-workflow
Inspect and maintain Android Gradle and Android Gradle Plugin workflows, including Gradle wrapper policy, AGP and Kotlin plugin versions, Java toolchains, Android SDK settings, namespaces, variants, flavors, signing config, version catalogs, dependencies, generated sources, build cache boundaries, and targeted…
release-readiness-workflow
Check Android release readiness without publishing by default, including versionCode and versionName, signing and keystore boundaries, release build types, R8/ProGuard, mapping outputs, app bundles, APKs, Play delivery handoffs, privacy, permissions, changelogs, and repository-owned release automation routing through…
testing-lint-workflow
Plan, run, filter, and triage Android tests and lint, including local unit tests, instrumentation and Compose UI test handoffs, Gradle variant tasks, lint configuration, lint baselines, failure explanations, emulator-aware validation routing, and readable next checks.