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 DaronVee/ccgg-skills-factory --skill skills-factorygit clone --depth 1 https://github.com/DaronVee/ccgg-skills-factoryWrote 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/daronvee/ccgg-skills-factory/skills-factory)<a href="https://agentmods.dev/skills/daronvee/ccgg-skills-factory/skills-factory"><img src="https://agentmods.dev/badge/skills/daronvee/ccgg-skills-factory/skills-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/daronvee/ccgg-skills-factory/skills-factory"><img src="https://agentmods.dev/badge/skills/daronvee/ccgg-skills-factory/skills-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.00054 | $0.07250 |
| Opus 5 | $0.00027 | $0.03625 |
| Sonnet 5 | $0.00011 | $0.01450 |
| Haiku 4.5 | $0.00005 | $0.00725 |
Grade A, and why
skills-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 12d 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 — 685 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Factory
A comprehensive meta-skill for creating, validating, evaluating, and iterating on production-ready Claude Code skills.
About Skills
Skills extend Claude Code's capabilities with specialized knowledge and workflows. They use a two-level progressive disclosure system:
- Description (YAML
descriptionfield) - Always loaded into context at startup. Claude uses this to decide when to invoke the skill. - Full Content (SKILL.md body + referenced files) - Loaded when the skill is invoked, either by Claude or the user.
Skills are filesystem-based and live in:
~/.claude/skills/- Personal skills (available across all projects).claude/skills/- Project skills (version-controlled, shared via git).claude/commands/- Backward-compatible location (also works)
Priority resolution (when same name exists at multiple levels): Enterprise > Personal > Project.
Note: Skills follow the Agent Skills open standard for cross-platform compatibility.
Context budget: Skill descriptions consume context. Total budget is ~2% of context window (default ~16k chars). If you have many skills, keep descriptions concise or use disable-model-invocation: true on rarely-needed skills.
Workspace Convention
CRITICAL: All eval and benchmark operations use this predetermined directory layout. Scripts, agents, and viewers depend on these exact paths. Do NOT deviate.
<skill-workspace>/
├── SKILL.md # The skill under development
├── evals/
│ ├── evals.json # Test cases (see SCHEMAS.md > evals.json)
│ ├── trigger-eval.json # Trigger queries (see SCHEMAS.md > trigger-eval.json)
│ └── files/ # Input files referenced by evals
├── iteration-<N>/ # One per eval cycle (iteration-0 = baseline)
│ ├── eval-<ID>/ # One per eval case
│ │ ├── with_skill/ # Runs WITH the skill loaded
│ │ │ ├── run-<M>/
│ │ │ │ ├── outputs/ # Executor output files + metrics.json
│ │ │ │ ├── transcript.md # Full executor transcript
│ │ │ │ ├── grading.json # Grader output (SCHEMAS.md > grading.json)
│ │ │ │ └── timing.json # Wall clock + token counts
│ │ │ └── ...
│ │ └── without_skill/ # Runs WITHOUT the skill (baseline)
│ │ └── run-<M>/
│ │ └── (same structure)
│ ├── benchmark.json # Aggregated stats (SCHEMAS.md > benchmark.json)
│ └── benchmark.md # Human-readable summary
├── description-optimization/ # Trigger description tuning
│ ├── results.json # run_loop.py output
│ └── report.html # Visual optimization report
└── history.json # Iteration progression tracker
What ships with it
28 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.
- agents/analyzer.md 10 KB
- agents/comparator.md 7.1 KB
- agents/grader.md 8.8 KB
- assets/eval_review.html 6.9 KB
- eval-viewer/generate_review.py 16 KB runs code
- eval-viewer/viewer.html 44 KB
- evals/evals.json 3.9 KB
- evals/trigger-eval.json 1.6 KB
- references/DEPLOYMENT_GUIDE.md 21 KB
- references/EVALUATION_GUIDE.md 16 KB
- references/FRONTMATTER_DECISION_GUIDE.md 14 KB
- references/SCHEMAS.md 9.6 KB
- references/SUBAGENT_PATTERNS.md 17 KB
- references/TROUBLESHOOTING.md 24 KB
- references/TWO_CLAUDE_METHODOLOGY.md 16 KB
- references/VALIDATION_PATTERNS.md 17 KB
- references/WORKFLOW_PATTERNS.md 17 KB
- scripts/__init__.py 33 B runs code
- scripts/aggregate_benchmark.py 8.1 KB runs code
- scripts/comprehensive_validate.py 28 KB runs code
- scripts/generate_report.py 8.2 KB runs code
- scripts/improve_description.py 8.2 KB runs code
- scripts/init_skill.py 14 KB runs code
- scripts/package_skill.py 7.3 KB runs code
- scripts/quick_validate.py 2.1 KB runs code
- scripts/run_eval.py 11 KB runs code
- scripts/run_loop.py 12 KB runs code
- scripts/utils.py 1.8 KB runs code
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.
- 12d ago First seen · 685 lines · 54 tokens per session scan A 10364ef36363
skills-factory is a skill published in the GitHub repository DaronVee/ccgg-skills-factory (5 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 7,250 once invoked, about $0.0003 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.
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…
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…