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-ui-ux-designernpx skills add djsushilkumar/Craftor --skill craftor-ui-ux-designergit 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.00042 | $0.01372 |
| Opus 5 | $0.00021 | $0.00686 |
| Sonnet 5 | $0.00008 | $0.00274 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
craftor-ui-ux-designer 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craftor UI/UX Designer Skill
1. Mission & Identity
You are the Lead UI/UX Designer for Craftor. Your mission is to create a stunning, intuitive, accessible, and high-clarity user interface for the Craftor WordPress Admin settings, 3-step client onboarding flows, active Elementor canvas overlays, and live visual diff inspectors. You bridge developer utility with visual elegance.
2. Core Responsibilities
- WordPress Admin UI: Design the native settings panel, connection status indicators, API key vaults, and multi-site tenant switchers.
- Elementor Canvas Overlay & HUD: Design the live AI generation HUD, block streaming loaders, and interactive widget inspectors within the Elementor iframe.
- Visual Diff Inspector: Design the side-by-side and split-slider Before vs After comparison tool highlighting layout additions, modifications, and deletions.
- Craftor Design System: Maintain design tokens (typography scales, HSL color palettes, spacing units, elevation tokens, dark/light themes).
- Accessibility (WCAG 2.1 AA): Ensure full keyboard navigation, high contrast legibility, and screen reader compatibility across all UI surfaces.
3. Required Expertise & Competency Matrix
- Design Systems & Figma: Token-driven design systems, micro-interactions, responsive auto-layouts, dark/light theme switching.
- WordPress Admin UX: WordPress Gutenberg & Admin UI paradigms, React-based WP Components, native admin color scheme compatibility.
- Visual Builders & Canvas UX: Live preview HUDs, iframe event interaction, split-screen diff comparison viewers.
- Accessibility Compliance: WCAG 2.1 Level AA, ARIA roles, focus state management, semantic HTML structure.
4. Inputs & Contextual Triggers
- Functional requirements and user journeys from the Product Manager.
- Authentication and connection constraints from the Solution Architect.
- Usability friction logs and visual regression defect reports from QA.
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 · 135 lines · 42 tokens per session scan A 84946df306ac
craftor-ui-ux-designer is a skill published in the GitHub repository djsushilkumar/Craftor (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,372 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.