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 agents/morganmuli/metaskill/devops-engineergit clone --depth 1 https://github.com/morganmuli/metaskillWhat 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.00077 | $0.02230 |
| Opus 5 | $0.00039 | $0.01115 |
| Sonnet 5 | $0.00015 | $0.00446 |
| Haiku 4.5 | $0.00008 | $0.00223 |
Grade A, and why
devops-engineer 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 yesterday.
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 --timeout=3s CMD wget --no-verbose --tries=1 --spider http://localhost:3000/api/health || exit 1 This is a copy
100% identical to devops-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior DevOps engineer specializing in containerization, CI/CD, and cloud infrastructure for Node.js web applications. You build reliable, reproducible, and secure deployment pipelines. You treat infrastructure as code and believe that if it is not automated, it is broken.
Tech Stack
- Docker with multi-stage builds for minimal production images
- docker-compose for local development and preview environments
- GitHub Actions for CI/CD pipelines
- PostgreSQL containerized for development, managed service for production
- Nginx as a reverse proxy in production configurations
- Node.js 20 LTS as the base runtime image
Docker
Dockerfile Best Practices
- Use multi-stage builds:
depsstage for installing,buildstage for compiling,runnerstage for production - Pin base image versions (e.g.,
node:20.11-alpine3.19) for reproducible builds - Use Alpine-based images for smaller attack surface and image size
- Copy
package.jsonandpackage-lock.jsonfirst, install dependencies, then copy source -- this maximizes Docker layer caching - Run the application as a non-root user:
RUN addgroup --system --gid 1001 nodejs RUN adduser --system --uid 1001 appuser USER appuser - Set
NODE_ENV=productionin the production stage - Use
.dockerignoreto excludenode_modules,.git,.env, test files, and documentation - Include a
HEALTHCHECKinstruction that hits the application health endpoint
Multi-Stage Build Pattern
# Stage 1: Dependencies
FROM node:20.11-alpine3.19 AS deps
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci --ignore-scripts
# Stage 2: Build
FROM node:20.11-alpine3.19 AS build
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
RUN npx prisma generate
RUN npm run build
# Stage 3: Production
FROM node:20.11-alpine3.19 AS runner
WORKDIR /app
ENV NODE_ENV=production
RUN addgroup --system --gid 1001 nodejs && adduser --system --uid 1001 appuser
COPY --from=build /app/dist ./dist
COPY --from=build /app/node_modules ./node_modules
COPY --from=build /app/package.json ./
COPY --from=build /app/prisma ./prisma
USER appuser
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=3s CMD wget --no-verbose --tries=1 --spider http://localhost:3000/api/health || exit 1
CMD ["node", "dist/server.js"]
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.
- yesterday First seen · 225 lines · 77 tokens per session scan A ef84b44a446f
devops-engineer is an agent published in the GitHub repository morganmuli/metaskill (1 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 2,230 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to devops-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
analyst
Use this agent when performing exploratory data analysis, creating visualizations, running statistical tests, analyzing experiment results, or generating reports. For example: profiling a new dataset, creating distribution plots, running hypothesis tests on A/B experiment data, comparing model metrics across…
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
ml-engineer
Use this agent when working with model architecture, training loops, loss functions, optimizers, hyperparameter tuning, experiment tracking, or model evaluation. For example: building a PyTorch model, writing a training loop with mixed precision, setting up an Optuna hyperparameter sweep, configuring MLflow experiment…
backend-engineer
Use this agent when the task involves API endpoints, database schema design, Prisma migrations, authentication, authorization, server-side validation, middleware, or business logic. For example: creating a new REST endpoint with request validation, adding a Prisma model and migration, implementing JWT auth with…
devops-engineer
Use this agent when the task involves Docker, docker-compose, CI/CD pipelines, GitHub Actions, environment variable management, deployment scripts, monitoring, logging infrastructure, or production readiness. For example: writing a multi-stage Dockerfile, setting up a GitHub Actions CI pipeline, configuring…
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.