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 oyi77/1ai-skills --skill deploy-agentgit clone --depth 1 https://github.com/oyi77/1ai-skillsWrote 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/oyi77/1ai-skills/deploy-agent)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/deploy-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/deploy-agent/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/oyi77/1ai-skills/deploy-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/deploy-agent.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.00017 | $0.01194 |
| Opus 5.5 | $0.00007 | $0.00478 |
| Sonnet 5.5 | $0.00003 | $0.00239 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
deploy-agent scanned grade A with 2 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Confirm the final report states the live URL/state you can independently curl-check. Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
assert subprocess.run(["git", "diff", "--quiet"], cwd=".").returncode == 0, "Dirty working tree" How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This agent ships code through a controlled pipeline with verification gates at every stage — build, test, and health checks before anything reaches production. Use it when a release must be reproducible and reversible. It refuses to call a deployment done until the live state is verified.
Deploy Agent
Quick Reference — see parent for full agent ecosystem.
The Deploy Agent ships artifacts to staging and production through a controlled pipeline with health checks, migration execution, automated rollbacks, and post-deploy monitoring. Its core design principle is reversibility: every deploy must have a tested rollback path before it begins.
When Not to Use
- Simple or one-off tasks — if the task is straightforward, direct execution is faster than structured methodology.
- Already established workflows — follow existing team conventions rather than introducing new frameworks.
- When automation overhead exceeds benefit — for very small scopes, the setup cost may not be justified.
Dependencies
- Python 3.8+ or Node.js 18+
- Access to relevant APIs/services for your specific use case
- Basic understanding of the domain concepts
Commands
# Refer to the skill's usage section for specific commands
# Adapt these to your workflow
Key Responsibilities
- Execute deployments with strategy: Support blue-green, rolling, canary, and hotfix strategies with zero-downtime guarantees
- Run database migrations: Apply schema changes in the correct order with dry-run validation and automated rollback scripts
- Verify post-deploy health: Run health checks, smoke tests, and monitor error rates for a configurable observation window
Code Example
"""Minimal deploy agent pattern — ship with verification."""
import json, subprocess, sys
from pathlib import Path
def deploy(target: str, tag: str, strategy: str = "rolling") -> dict:
# 1. Pre-deploy checks
assert subprocess.run(["git", "diff", "--quiet"], cwd=".").returncode == 0, "Dirty working tree"
assert subprocess.run([sys.executable, "-m", "pytest", "-x", "-q"]).returncode == 0
# 2. Build artifact
build = subprocess.run(["docker", "build", "-t", f"app:{tag}", "."], capture_output=True, text=True)
if build.returncode != 0:
return {"status": "failed", "error": build.stderr}
# 3. Run migrations (dry-run first)
dry = subprocess.run([sys.executable, "-m", "alembic", "upgrade", "--sql", "head"], capture_output=True, text=True)
print(f"Migration SQL:\n{dry.stdout}")
# 4. Deploy
push = subprocess.run(["docker", "push", f"app:{tag}"])
if target == "production":
subprocess.run(["kubectl", "set", "image", f"deployment/app=app:{tag}"])
subprocess.run(["kubectl", "rollout", "status", "deployment/app"])
return {
"target": target, "tag": tag, "strategy": strategy,
"migration_applied": True, "rollback": f"kubectl rollout undo deployment/app"
}
if __name__ == "__main__":
result = deploy(sys.argv[1], sys.argv[2], sys.argv[3] if len(sys.argv) > 3 else "rolling")
print(json.dumps(result, indent=2))
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 Changed · +11 lines e16c081c3fac
- 1mo ago First seen · 119 lines · 17 tokens per session scan A cb17d8aa2f80
deploy-agent is a skill published in the GitHub repository oyi77/1ai-skills (17 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 1,194 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
github-repo-management
Clone, create, fork repos; manage remotes, releases.
aidd-log
Document completed epics in a structured changelog with emoji categorization. Use when the user asks to log changes, update the changelog, or after completing a significant feature or epic.
chinese-commit-conventions
A Chinese-language reference for writing commit messages and changelogs, which record code changes and releases.
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.