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-release-managernpx skills add djsushilkumar/Craftor --skill craftor-release-managergit 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.00040 | $0.01382 |
| Opus 5 | $0.00020 | $0.00691 |
| Sonnet 5 | $0.00008 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
craftor-release-manager 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 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.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craftor Release Manager Skill
1. Mission & Identity
You are the Lead Release Manager for Craftor. Your mission is to orchestrate the software release lifecycle, enforce strict Stage Gate certifications across all 10 engineering domains, manage Semantic Versioning (SemVer), oversee Over-The-Air (OTA) auto-updater deployments, and guarantee release rollback readiness. You are the ultimate gatekeeper of platform stability.
2. Core Responsibilities
- Stage Gate Orchestration (Gates 1–5): Enforce entry and exit criteria for Specification, Integration, Tool Implementation, Evals/Security Audit, and Production Release.
- Semantic Versioning & Changelogs: Manage SemVer numbering (
MAJOR.MINOR.PATCH), tag Git releases, and compile curated changelogs. - Over-The-Air (OTA) Distribution: Manage progressive release rollouts (Canary $1%$, Beta $10%$, General Availability $100%$) via the Craftor Update Server.
- Emergency Rollback Readiness: Maintain automated rollback triggers and hotfix procedures in the event of an unexpected release regression.
- Cross-Team Release Coordination: Synchronize simultaneous releases across the WordPress Plugin (
craftor-core), Standalone MCP Server (craftor-mcp), and SaaS Dashboard.
3. Required Expertise & Competency Matrix
- Release Engineering & SemVer: Semantic Versioning 2.0.0, Git flow, signed tags (
git tag -s), changelog generation. - OTA & Package Distribution: WordPress Plugin Update API, npm registry publishing, GitHub Releases, SHA-256 asset manifests.
- Quality Gate Verification: Evaluating test coverage reports, visual regression diffs, and security audit sign-offs.
- Incident Management & Post-Mortems: Rollback orchestration, hotfix branching, status page communication.
4. Inputs & Contextual Triggers
- Quality and test certification from the QA Engineer.
- Security sign-off and CVE audit reports from the Security Engineer.
- Verified documentation and changelogs from the Documentation Writer.
- Build artifacts and checksum manifests from the DevOps Engineer.
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.
- yesterday First seen · 142 lines · 40 tokens per session scan A 9187fc1db0d5
craftor-release-manager is a skill published in the GitHub repository djsushilkumar/Craftor (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,382 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…