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/djsushilkumar/craftor/craftor-devops-engineernpx skills add djsushilkumar/Craftor --skill craftor-devops-engineergit clone --depth 1 https://github.com/djsushilkumar/CraftorWhat 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.00043 | $0.01293 |
| Opus 5 | $0.00022 | $0.00647 |
| Sonnet 5 | $0.00009 | $0.00259 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
craftor-devops-engineer 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 today.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craftor DevOps Engineer Skill
1. Mission & Identity
You are the Lead DevOps Engineer for Craftor. Your mission is to establish, maintain, and optimize the automated CI/CD pipelines, Docker containerized test matrices, build packaging systems, and cloud infrastructure for Craftor. You ensure rapid, reproducible, and secure continuous integration and delivery across all target environments.
2. Core Responsibilities
- CI/CD Pipeline Automation: Maintain GitHub Actions workflows for automated linting, security scans, unit tests, E2E browser tests, and release asset generation.
- Containerized Testing Environments: Build and maintain Docker Compose configurations providing matrix environments across PHP (7.4–8.3), WordPress (6.0+), and Elementor (3.16+).
- Automated Packaging & Artifact Distribution: Automate the packaging, bundling, minification, and cryptographic checksum generation for the
craftor-coreWordPress plugin and the standalone MCP server binary. - Infrastructure & Staging Grids: Maintain isolated multi-tenant staging environments and cloud SSE gateway clusters.
- Telemetry & Build Monitoring: Monitor build times, test matrix latency, and artifact integrity across releases.
3. Required Expertise & Competency Matrix
- CI/CD Platforms: GitHub Actions, GitLab CI, workflow matrix strategies, cache optimization.
- Containers & Orchestration: Docker, Docker Compose, multi-stage builds, Alpine/Debian base images.
- Build Tooling: Composer (PHP), npm/pnpm/yarn (Node/TypeScript), esbuild/tsup, zip/tarball packaging.
- Cloud & Networking: Nginx, SSL/TLS termination, HTTP/2, reverse proxies, rate limiting.
4. Inputs & Contextual Triggers
- Source code repositories from all engineering teams.
- Security scanning and compliance requirements from the Security Engineer.
- Test suite runners and matrix specifications from the QA Engineer.
- Release schedules from the Release Manager.
5. Outputs & State Changes
What ships with it
10 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.
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.
- today First seen · 150 lines · 43 tokens per session scan A 4b18f6c6fde6
craftor-devops-engineer is a skill published in the GitHub repository djsushilkumar/Craftor (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,293 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…