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/firstp1ck/pi-coding-agent-forge/deployment-automationnpx skills add Firstp1ck/pi-coding-agent-forge --skill deployment-automationgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWrote 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/firstp1ck/pi-coding-agent-forge/deployment-automation)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/deployment-automation"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/deployment-automation.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.00047 | $0.02010 |
| Opus 5 | $0.00023 | $0.01005 |
| Sonnet 5 | $0.00009 | $0.00402 |
| Haiku 4.5 | $0.00005 | $0.00201 |
Grade A, and why
deployment-automation 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 4d 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.
curl -s -o /dev/null -w "%{http_code}" http://localhost:<port>/health How it starts
The opening of the file, as written. The whole thing — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Automation
Manage Docker Compose deployments, container lifecycle, image updates, and rollbacks.
Quick Start
Deploy a Compose Stack
# Start services
docker compose up -d
# Start with rebuild
docker compose up -d --build
# Check status
docker compose ps
Update a Running Service
# Pull latest images
docker compose pull
# Recreate with new images
docker compose up -d --remove-orphans
# Verify health
docker compose ps
docker compose logs --tail=20 <service>
Docker Compose Management
Lifecycle Commands
# Start all services
docker compose up -d
# Stop all services (preserves volumes)
docker compose down
# Stop and remove volumes (DESTRUCTIVE)
docker compose down -v
# Restart a specific service
docker compose restart <service>
# Scale a service
docker compose up -d --scale <service>=3
# View logs
docker compose logs -f <service>
docker compose logs --tail=50 <service>
Stack Health Check
# List all containers with status
docker compose ps --format "table {{.Name}}\t{{.Status}}\t{{.Ports}}"
# Check resource usage
docker stats --no-stream --format "table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}"
# Inspect a specific container
docker inspect <container> | jq '.[0].State'
Image Update Workflow
Safe update process with rollback path:
Step 1: Pre-Update Checks
# Record current state
docker compose ps > /tmp/pre-update-state.txt
docker compose config --images > /tmp/current-images.txt
# Check current image digests
docker compose images --format "table {{.Repository}}\t{{.Tag}}\t{{.ID}}"
Step 2: Pull New Images
# Pull latest images
docker compose pull
# Compare image IDs (see if anything changed)
docker compose images --format "table {{.Repository}}\t{{.Tag}}\t{{.ID}}"
Step 3: Deploy Update
# Recreate containers with new images
docker compose up -d --remove-orphans
# Wait for services to stabilize
sleep 10
# Verify all containers are healthy
docker compose ps
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.
- 4d ago First seen · 399 lines · 47 tokens per session scan A 9af101fc70e2
deployment-automation is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (77 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,010 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.