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 alirezarezvani/claude-code-skill-factory --skill slash-command-factorygit clone --depth 1 https://github.com/alirezarezvani/claude-code-skill-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/alirezarezvani/claude-code-skill-factory/slash-command-factory)<a href="https://agentmods.dev/skills/alirezarezvani/claude-code-skill-factory/slash-command-factory"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-code-skill-factory/slash-command-factory.svg" alt="Measured on agentmods" 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.00057 | $0.05945 |
| Opus 5 | $0.00028 | $0.02972 |
| Sonnet 5 | $0.00011 | $0.01189 |
| Haiku 4.5 | $0.00006 | $0.00594 |
Grade A, and why
slash-command-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 8d 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 — 1,007 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slash Command Factory
A comprehensive system for generating production-ready Claude Code slash commands through a simple question-based workflow.
What This Skill Does
This skill helps you create custom slash commands for Claude Code by:
- Asking 5-7 straightforward questions about your command needs
- Generating complete command .md files with proper YAML frontmatter
- Providing 10 powerful preset commands for common use cases
- Validating command format and syntax
- Creating well-organized folder structures
- Offering installation guidance
Output: Complete slash commands ready to use in Claude Code
Official Command Structure Patterns
This skill generates commands following three official patterns from Anthropic documentation:
Pattern A: Simple (Context → Task)
Best for: Straightforward tasks with clear input/output Example: Code review, file updates, simple analysis Official Reference: code-review.md
Structure:
---
allowed-tools: Bash(git diff:*), Bash(git log:*)
description: Purpose description
---
## Context
- Current state: !`bash command`
- Additional data: !`another command`
## Your task
[Clear instructions with numbered steps]
[Success criteria]
When to use:
- Simple, focused tasks
- Quick analysis or reviews
- Straightforward workflows
- 1-3 bash commands for context
Pattern B: Multi-Phase (Discovery → Analysis → Task)
Best for: Complex discovery and documentation tasks Example: Codebase analysis, comprehensive audits, system mapping Official Reference: codebase-analysis.md
Structure:
---
allowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(grep:*), Bash(wc:*), Bash(du:*)
description: Comprehensive purpose
---
# Command Title
## Phase 1: Project Discovery
### Directory Structure
!`find . -type d | sort`
### File Count Analysis
!`find . -type f | wc -l`
## Phase 2: Detailed Analysis
[More discovery commands]
[File references with @]
## Phase 3: Your Task
Based on all discovered information, create:
1. **Deliverable 1**
- Subsection
- Details
2. **Deliverable 2**
- Subsection
- Details
At the end, write output to [filename].md
What ships with it
6 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.
- 8d ago First seen · 1,007 lines · 57 tokens per session scan A 5e78a5c9bb1e
slash-command-factory is a skill published in the GitHub repository alirezarezvani/claude-code-skill-factory (859 stars, last pushed 9mo ago), licensed MIT. It adds 57 tokens to every session and 5,945 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-30.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
grill-me
Two modes, picked from the file you point it at. Contract mode grills a claude-contract.md line by line until every line is a thing Claude must always do or must never do, editing that file in place and creating nothing new. Brief mode interrogates a design brief until it has no soft spots left, then produces a…
information-architecture
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or UI.
design-tokens
Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.