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/nikitadmitrieff/auto-co-meta/devopsnpx skills add NikitaDmitrieff/auto-co-meta --skill devopsgit clone --depth 1 https://github.com/NikitaDmitrieff/auto-co-metaWhat 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.00048 | $0.01226 |
| Opus 5 | $0.00024 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
devops 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Skill
Deploy and manage cloud infrastructure across Vercel, Railway, Supabase, and GitHub Actions.
When to Use
- Deploy frontends and serverless functions to Vercel
- Deploy backend services to Railway
- Manage databases, auth, and storage with Supabase
- Set up CI/CD pipelines with GitHub Actions
- Monitor deployments and debug production issues
- Manage environment variables and secrets
Platform Selection
| Need | Choose |
|---|---|
| Frontend / Next.js / static sites | Vercel |
| Serverless API routes / edge functions | Vercel |
| Long-running backend services | Railway |
| Background workers / cron jobs | Railway |
| PostgreSQL database | Supabase |
| User authentication | Supabase Auth |
| File/image storage | Supabase Storage |
| Realtime subscriptions | Supabase Realtime |
| Edge functions (Deno) | Supabase Edge Functions |
| CI/CD pipelines | GitHub Actions |
Quick Start
# Vercel - deploy frontend
vercel deploy # Preview deployment
vercel deploy --prod # Production deployment
# Railway - deploy backend
railway up # Deploy current directory
railway logs # View service logs
# Supabase - manage database
supabase db push # Push migrations to remote
supabase migration new feat_name # Create new migration
# GitHub Actions - CI/CD
gh workflow run deploy.yml # Trigger workflow manually
gh run list # View recent runs
Command Reference
Vercel
# Deployments
vercel deploy # Deploy to preview
vercel deploy --prod # Deploy to production
vercel ls # List recent deployments
vercel inspect <url> # Deployment details
vercel logs <url> # View function logs
vercel redeploy # Redeploy latest
# Environment variables
vercel env pull .env.local # Pull env vars locally
vercel env add SECRET_KEY # Add env var (interactive)
vercel env rm SECRET_KEY # Remove env var
# Project management
vercel link # Link local dir to project
vercel project ls # List all projects
# Domains
vercel domains add example.com # Add custom domain
vercel domains ls # List domains
What ships with it
19 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.
- references/docker-basics.md 5.7 KB
- references/docker-compose.md 4.7 KB
- references/gcloud-platform.md 6.9 KB
- references/gcloud-services.md 5.8 KB
- references/kubernetes-basics.md 1.7 KB
- references/kubernetes-helm-advanced.md 1.7 KB
- references/kubernetes-helm.md 1.8 KB
- references/kubernetes-kubectl.md 1.7 KB
- references/kubernetes-security-advanced.md 1.8 KB
- references/kubernetes-security.md 1.7 KB
- references/kubernetes-troubleshooting-advanced.md 1.4 KB
- references/kubernetes-troubleshooting.md 1.4 KB
- references/kubernetes-workflows-advanced.md 1.3 KB
- references/kubernetes-workflows.md 1.6 KB
- scripts/docker_optimize.py 11 KB runs code
- scripts/requirements.txt 471 B
- scripts/tests/requirements.txt 52 B
- scripts/tests/test_cloudflare_deploy.py 9.0 KB runs code
- scripts/tests/test_docker_optimize.py 13 KB runs code
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 First seen · 175 lines · 48 tokens per session scan A 86ea91a9f1a5
devops is a skill published in the GitHub repository NikitaDmitrieff/auto-co-meta (43 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,226 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
add-code-quality-hook
Recipe for wiring a new linter into Opik's unified 🐙 Code Quality pipeline (pre-commit + CI). Use when adding a pre-commit-driven linter/formatter to the repo — enumerates every file that must change (.pre-commit-config.yaml, scripts/precommit-hook-descriptions.tsv, scripts/precommit-detect-hooks.py…
eliza-cloud
Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …
eliza-cloud-manage-domain
Use after a domain has been purchased through Eliza Cloud (via the eliza-cloud-buy-domain skill) when the user wants to look at, edit, or remove a domain or its DNS records. Covers org-wide domain listing, per-app DNS record CRUD on cloudflare-managed zones, status re-sync, external-attachment verification, and…
github
Interact with GitHub using the gh CLI to manage repositories, issues, pull requests, CI/CD workflow runs, and API queries. Use when the user asks to create, list, view, merge, or close pull requests and issues; check CI status or workflow run logs; query the GitHub API for repository data; or perform any GitHub…
deploy-status
Check civitai PROD deployment status across the live Tekton -> Flux -> Flagger chain on the DataPacket cluster (kubectl, read-only). Tekton/Flagger cluster state is the primary truth; the GitHub Deployments API is kept as a public cross-check. Use to see where a deploy is in the chain, watch it to completion, or debug…
email-setup
Set up this assistant's own [name].vellum.me domain and email address (one-time setup).