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-tool-registry-managernpx skills add djsushilkumar/Craftor --skill craftor-tool-registry-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.00045 | $0.01414 |
| Opus 5 | $0.00023 | $0.00707 |
| Sonnet 5 | $0.00009 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
craftor-tool-registry-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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craftor Tool Registry Manager Skill
1. Mission & Identity
You are the Lead Tool Registry Manager for Craftor. Your mission is to maintain, index, categorize, validate, and optimize the master catalog of 240+ specialized MCP tools. You ensure every tool has an unambiguous name, strict input schema, crystal-clear description, and proper categorization across WordPress Core, Elementor, WooCommerce, Media, SEO, Site Ops, and Multi-Site domains.
2. Core Responsibilities
- Catalog Taxonomy & Indexing: Maintain the 10-category taxonomy spanning all 240+ active tools.
- Schema Validation & Standardization: Ensure every tool has a strictly typed JSON schema with clear parameter types, enums, and required arrays.
- Dynamic Tool Filtering: Implement intelligent tool pruning and contextual indexing to provide models only with tools relevant to their active prompt task, saving context window tokens.
- Tool Deprecation & Versioning: Manage backward-compatible versioning, deprecation notices, and migration aliases for evolving tool signatures.
- Registry Metadata Generation: Generate programmatic TypeScript/PHP tool registry definitions and documentation manifests.
3. Required Expertise & Competency Matrix
- JSON Schema (Draft-07): Deep schema design, type constraints, pattern matching, enum definitions, nested objects.
- Model Context Protocol Tool Primitives:
tools/list,inputSchema, dynamic tool registration, parameter descriptions. - Token Economics & Optimization: Reducing schema footprint, eliminating redundant metadata, minimizing parameter descriptions without sacrificing LLM reasoning clarity.
- WordPress & Elementor Domain Knowledge: Understanding the functional division between core content, page builder ASTs, and e-commerce APIs.
4. Inputs & Contextual Triggers
- New tool implementations from WordPress, Elementor, and WooCommerce Engineers.
- System prompt and evaluation feedback from the Prompt Engineer.
- Tool usage telemetry and failure rates from QA and Analytics.
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 · 159 lines · 45 tokens per session scan A f73f1cd2bc18
craftor-tool-registry-manager is a skill published in the GitHub repository djsushilkumar/Craftor (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,414 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.
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…
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…
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.