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 commands/alirezarezvani/claude-code-skill-factory/readmegit 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/commands/alirezarezvani/claude-code-skill-factory/readme)<a href="https://agentmods.dev/commands/alirezarezvani/claude-code-skill-factory/readme"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-code-skill-factory/readme.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 | $0.00000 | $0.02123 |
| Opus 5 | $0.00000 | $0.01061 |
| Sonnet 5 | $0.00000 | $0.00425 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade B, and why
README scanned grade B with 1 finding 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 4d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
/validate-output prompt # Check prompt quality How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Factory Slash Commands
5 essential commands for building Skills, Prompts, and Agents from start to finish.
🎯 Complete Workflow Commands
/build → Start building (invoke orchestrator)
/validate-output → Check quality
/install-skill → Install outputs
/test-factory → Test functionality
/factory-status → Track progress
📋 The 5 Commands
1. /build - Start Building
Purpose: Main entry point - invoke factory-guide orchestrator or specialists
Usage:
/build # Ask what to build
/build skill # Directly invoke skills-guide
/build prompt # Directly invoke prompts-guide
/build agent # Directly invoke agents-guide
What happens:
- Invokes appropriate navigation agent
- Guides through Q&A (3-11 questions)
- Generates complete output
- Validates and helps install
When to use: Start of any factory workflow
2. /validate-output - Quality Check
Purpose: Validate generated skills/prompts/agents
Usage:
/validate-output skill [path] # Check skill format
/validate-output prompt # Check prompt quality
/validate-agent [path] # Check agent format
What it checks:
- ✅ YAML frontmatter validity
- ✅ Naming conventions (kebab-case)
- ✅ Required files present
- ✅ Format correctness
- ✅ Quality standards
When to use: After generation, before installation
3. /install-skill - Installation Helper
Purpose: Step-by-step installation guidance
Usage:
/install-skill [path-to-skill] # Install skill
/install-skill [path-to-agent] # Install agent (works for both)
What it provides:
- Multiple installation options (Desktop, Code, Browser)
- Detailed commands for each method
- Verification steps
- Troubleshooting help
When to use: After validation passes
4. /test-factory - Quick Test
Purpose: Test generated outputs work correctly
Usage:
/test-factory skill [skill-name] # Test skill
/test-factory agent [agent-name] # Test agent
/test-factory prompt # Test prompt
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.
- 4d ago First seen · 405 lines · 0 tokens per session scan B c6d3e87da84c
README is a command published in the GitHub repository alirezarezvani/claude-code-skill-factory (855 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,123 tokens. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
create-skill
Create an AI skill from any source (URL, repo, PDF, video, notebook, etc.).
sync-config
Sync a scraping config's URLs against the live documentation site.
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
statusbar
Show current status-bar config and list available styles + themes.
docs-update
You are executing the /dogma:docs-update command. Your task is to synchronize documentation across README files and wiki articles, ensuring everything is up-to-date.
sanitize-git
You are executing the /dogma:sanitize-git command. Your task is to find and remove AI/Claude traces from git history and fix tracking issues where files that should be excluded are still being tracked.