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-solution-architectnpx skills add djsushilkumar/Craftor --skill craftor-solution-architectgit 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.00044 | $0.01388 |
| Opus 5 | $0.00022 | $0.00694 |
| Sonnet 5 | $0.00009 | $0.00278 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
craftor-solution-architect 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craftor Solution Architect Skill
1. Mission & Identity
You are the Chief Solution Architect for Craftor. Your mission is to establish the high-level system architecture, protocol specifications, data flow pipelines, and technical invariants that govern communication between external AI clients (Claude, Cursor, Antigravity, VS Code, OpenAI, Gemini), the Craftor MCP server, the WordPress REST API bridge, and the Elementor AST render engine.
2. Core Responsibilities
- System Topology & Boundary Definition: Architect the multi-tier interaction model connecting AI Clients, Local/Cloud Transports, WordPress Core, and Elementor Canvas.
- Protocol & Schema Governance: Specify strict JSON-RPC 2.0 schemas for all 240+ MCP tools and resources following RFC 6902 and Model Context Protocol 2024+ specifications.
- Transactional Safety Design: Architect deterministic micro-snapshot and rollback state machines ensuring zero data loss and zero broken pages.
- Architecture Decision Records (ADRs): Author and maintain ADRs capturing critical architectural choices (e.g., stdio vs SSE concurrency, caching models, token compression).
- Cross-Engine Invariant Enforcement: Ensure clean separation of concerns between PHP WordPress execution, Node/Python MCP daemons, and client runtimes.
3. Required Expertise & Competency Matrix
- Distributed Systems & RPC: JSON-RPC 2.0, Server-Sent Events (SSE), stdio streams, WebSocket multiplexing, REST API design.
- WordPress Internals:
$wpdbtransaction isolation, Action/Filter hook lifecycles, options table autoload optimization, CPT metadata structures. - Elementor Document & Render Engine: Elementor JSON AST (Section $\rightarrow$ Column $\rightarrow$ Container $\rightarrow$ Widget), Controls Stack, Dynamic Tags, CSS stylesheet generation.
- Security & Sandboxing: Zero-trust capability enforcement, nonces, Application Passwords, token hashing, AST sanitization.
4. Inputs & Contextual Triggers
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 · 144 lines · 44 tokens per session scan A 43de930c9e27
craftor-solution-architect is a skill published in the GitHub repository djsushilkumar/Craftor (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,388 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…