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 Omar-Obando/qwen-orchestrator --skill deploymentgit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/deployment)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/deployment"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/deployment/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/omar-obando/qwen-orchestrator/deployment"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/deployment.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.00037 | $0.01009 |
| Opus 5 | $0.00018 | $0.00504 |
| Sonnet 5 | $0.00007 | $0.00202 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
deployment 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 9d 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.
HEALTHCHECK --interval=30s CMD wget --no-verbose --tries=1 --spider http://localhost:3000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Skill — Release Engineering
This skill provides comprehensive deployment and release management guidance.
Deployment Checklist
Pre-Deployment
- All tests pass (unit, integration, e2e)
- Code review approved
- Security scan clean
- Performance baselines met
- Database migrations tested
- Environment variables documented
- Rollback plan documented
- Monitoring/alerting configured
Deployment Steps
- Tag release in version control
- Build production artifacts
- Run smoke tests against staging
- Deploy to production
- Verify health checks pass
- Monitor error rates for 15 minutes
- Announce deployment
Post-Deployment
- Verify all critical user journeys
- Check error rates and latency
- Verify monitoring dashboards
- Update release notes
- Notify stakeholders
CI/CD Pipeline Template
# .github/workflows/ci.yml
name: CI/CD Pipeline
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
jobs:
quality:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm run lint
- run: npm run typecheck
- run: npm run test:unit
- run: npm run test:integration
- run: npm run build
security:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npx audit-ci --moderate
- run: npx snyk test
deploy:
needs: [quality, security]
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm run deploy:production
Docker Best Practices
# Multi-stage build for minimal image
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --ignore-scripts
COPY . .
RUN npm run build
FROM node:20-alpine AS runtime
WORKDIR /app
RUN addgroup -g 1001 appgroup && adduser -u 1001 -G appgroup -s /bin/sh -D appuser
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./
USER appuser
EXPOSE 3000
HEALTHCHECK --interval=30s CMD wget --no-verbose --tries=1 --spider http://localhost:3000/health || exit 1
CMD ["node", "dist/index.js"]
What ships with it
1 file 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.
- 9d ago First seen · 169 lines · 37 tokens per session scan A 289b58e23e7d
deployment is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,009 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
DevOps Avançado com Jenkins e Docker
Implementação de práticas de DevOps utilizando Jenkins e Docker.
Implementacao-de-DevOps-Com-Jenkins-e-Docker
O objetivo desta skill é ensinar como implementar práticas de DevOps utilizando Jenkins e Docker, incluindo a configuração de pipelines de entrega contínua e a orquestração de contêineres. Com isso, os participantes poderão entender como automatizar e otimizar o processo de desenvolvimento e entrega de software.
aplicacao-de-tecnologias-de-devops
Ensina como implementar práticas de DevOps utilizando ferramentas como Docker, Kubernetes e Jenkins.
devops-com-jenkins-e-docker
Guia prático para implementação de pipelines de entrega contínua utilizando Jenkins e Docker.
devops-com-kubernetes
Aprenda a automatizar pipelines de entrega contínua e garantir a escalabilidade de aplicativos utilizando Kubernetes e ferramentas de DevOps como Jenkins e GitLab CI/CD.
devops-para-ambientes-de-containers
O objetivo deste guia é fornecer uma visão geral de como implementar práticas DevOps em ambientes que utilizam contêineres, garantindo a entrega contínua e confiável de software.