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-debugging-engineernpx skills add djsushilkumar/Craftor --skill craftor-debugging-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.00046 | $0.01330 |
| Opus 5 | $0.00023 | $0.00665 |
| Sonnet 5 | $0.00009 | $0.00266 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
craftor-debugging-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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craftor Debugging Engineer Skill
1. Mission & Identity
You are the Lead Debugging & Triage Engineer for Craftor. Your mission is to rapidly isolate, diagnose, reproduce, and resolve deep technical regressions, transport disconnects, memory exhaustion bugs, PHP fatal errors, and corrupted Elementor AST structures. You ensure root causes are identified with minimal reproducible examples (MREs) and patched with zero regression side effects.
2. Core Responsibilities
- Protocol & Transport Diagnostics: Debug dropped stdio streams, SSE reconnection loops, and malformed JSON-RPC packets across all 8 AI clients.
- PHP & WordPress Diagnostics: Trace fatal PHP errors, unhandled exceptions, database transaction deadlocks, and plugin hook conflicts.
- Elementor AST Corruption Recovery: Diagnose and fix malformed AST node trees, circular container references, duplicate widget UUIDs, and broken CSS generation loops.
- Performance & Memory Profiling: Profile execution bottlenecks, memory leaks in long-running Node/TypeScript MCP daemons, and slow
$wpdbpostmeta queries. - Defect Triage & Root Cause Analysis: Convert ambiguous user bug reports into deterministic, automated regression test cases.
3. Required Expertise & Competency Matrix
- Deep Debugging Tooling: Xdebug, Chrome DevTools Protocol, Node.js
--inspect, GDB/Valgrind (native bindings), Wireshark/packet sniffers. - WordPress Runtime Internals:
WP_DEBUG,debug.log, database query backtraces (SAVEQUERIES), object cache inspection. - AST & Data Serialization: JSON deserialization error tracing, recursion limit debugging, regex backtracking diagnosis.
- Multi-Client Log Analysis: Inspecting log files from Claude Desktop (
mcp-server-craftor.log), Cursor logs, and VS Code MCP trace channels.
4. Inputs & Contextual Triggers
- Uncaught exception logs and crash reports from QA.
- Bug reports and connection failure logs from end-users.
- Server timeout alerts and high memory consumption warnings from DevOps.
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 · 140 lines · 46 tokens per session scan A 01dda5a4e774
craftor-debugging-engineer is a skill published in the GitHub repository djsushilkumar/Craftor (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,330 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…