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 skills add hamzaPixl/pixl-ai --skill skill-factorygit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hamzapixl/pixl-ai/skill-factory)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/skill-factory"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/skill-factory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/skill-factory"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/skill-factory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00108 | $0.01146 |
| Opus 5.5 | $0.00043 | $0.00458 |
| Sonnet 5.5 | $0.00022 | $0.00229 |
| Haiku 4.5 | $0.00011 | $0.00115 |
Grade A, and why
skill-factory 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 1mo ago.
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.
Overview
Unified skill for creating and maintaining Claude Code skills. Combines skill creation, detection from session patterns, and quality improvement into one workflow.
Required References
Before generating or auditing, read references/skill-authoring-guide.md for the complete authoring guide (anatomy, progressive disclosure, writing style, validation checklist).
For the original Anthropic skill-creator methodology, see references/skill-creator-original.md.
Mode Detection
- If input is a session transcript or "detect"/"extract" → Mode B (Detect)
- If input points to an existing skill directory or mentions "improve"/"audit" → Mode C (Improve)
- Otherwise → Mode A (Create)
Mode A: Create
Build a new skill from a description or requirements.
Step A1: Gather Requirements
Ask targeted questions (avoid overwhelming — 2-3 at a time):
- What the skill does and when to use it
- Concrete usage examples ("What would a user say to trigger this?")
- Input parameters and expected output format
- Step-by-step process
Step A2: Plan Resources
Analyze the workflow to identify reusable resources:
- Scripts — Code that would be rewritten each time (e.g.,
scripts/rotate_pdf.py) - References — Knowledge rediscovered each time (e.g.,
references/schema.md) - Assets — Boilerplate needed each time (e.g.,
assets/template/)
Step A3: Design
- Define YAML frontmatter:
name,description(with trigger phrases),allowed-tools,argument-hint - Break the workflow into numbered steps
- Identify conditional steps and parallel execution points
- Define what each step produces
Step A4: Generate
- Create the skill directory:
skills/<skill-name>/ - Write
SKILL.mdwith frontmatter and step instructions - Create reference/script/asset files as needed
- Ensure instructions are clear enough for Claude to follow autonomously
CRITICAL: Follow the writing style in references/skill-authoring-guide.md — imperative form, third-person description, specific trigger phrases.
What ships with it
2 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.
- 1mo ago First seen · 140 lines · 108 tokens per session scan A d82031bd0aff
skill-factory is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 108 tokens to every session and 1,146 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…