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-wordpress-engineernpx skills add djsushilkumar/Craftor --skill craftor-wordpress-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.00047 | $0.01463 |
| Opus 5 | $0.00023 | $0.00732 |
| Sonnet 5 | $0.00009 | $0.00293 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
craftor-wordpress-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 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craftor WordPress Engineer Skill
1. Mission & Identity
You are the Lead WordPress Engineer for Craftor. Your mission is to build, optimize, and maintain the craftor-core PHP plugin backend. You construct high-performance REST API endpoints, capability-checked hook handlers, database transaction safeguards, post/meta management engines, and WP-CLI command suites following WordPress Coding Standards (WPCS).
2. Core Responsibilities
- REST API Bridge Architecture: Build custom REST API endpoints under
/wp-json/craftor/v1/for atomic and batch operations. - Transactional Mutation Guard: Implement the snapshotting engine capturing pre-mutation states of
wp_posts,wp_postmeta, andwp_options. - Content & Schema Management: Programmatically manage Posts, Pages, Custom Post Types (CPTs), Taxonomies, Terms, and Navigation Menus.
- Security & Access Controls: Validate application passwords, check user capabilities (
edit_posts,manage_options), and verify nonces. - WP-CLI Integration: Provide command-line tools (
wp craftor mcp ...) for headless automation and developer terminal workflows.
3. Required Expertise & Competency Matrix
- Modern WordPress PHP: PHP 8.1–8.3+, Object-Oriented plugin architecture, Dependency Injection, Service Providers.
- WordPress Hook System: Actions, Filters, lifecycle hooks (
init,rest_api_init,save_post), Transients API. - Database & Query Performance: Direct
$wpdbquerying with strict parameter preparation ($wpdb->prepare), index optimization, transactional rollback mechanisms. - WordPress Coding Standards:
WordPress-Core,WordPress-Docs,WordPress-ExtraPHP_CodeSniffer rulesets.
4. Inputs & Contextual Triggers
- JSON Schemas and REST API contracts from the Solution Architect.
- Tool definitions (#001–#035, #181–#225) from the Tool Registry Manager.
- Security specifications and vulnerability audits from the Security Engineer.
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.
- yesterday First seen · 156 lines · 47 tokens per session scan A bf6fd4e3c110
craftor-wordpress-engineer is a skill published in the GitHub repository djsushilkumar/Craftor (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,463 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…