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/validate-outputgit 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/validate-output)<a href="https://agentmods.dev/commands/alirezarezvani/claude-code-skill-factory/validate-output"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-code-skill-factory/validate-output.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.02062 |
| Opus 5 | $0.00000 | $0.01031 |
| Sonnet 5 | $0.00000 | $0.00412 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade D, and why
validate-output scanned grade D with 2 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 5d 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 Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- ✅ No destructive operations (no `rm -rf`, `git push --force`) How it starts
The opening of the file, as written. The whole thing — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate-output - Validate Generated Skills, Prompts, Agents, or Hooks
Check that your generated output is properly formatted and ready to use.
Usage
/validate-output skill [path]
/validate-output prompt
/validate-agent [path]
/validate-output hook [path]
What This Command Does
Validates generated output and creates distribution files:
- ✅ YAML frontmatter is correct
- ✅ Naming conventions followed (kebab-case)
- ✅ Required files present
- ✅ Format is proper
- ✅ Quality standards met
- ✅ Creates ZIP file (if validation passes for skills)
Validate a Skill
/validate-output skill generated-skills/my-skill
Checks:
- YAML Frontmatter:
---
name: skill-name-kebab-case ✅ Check format
description: One-line description ✅ Check present
---
- Naming:
- ✅ Skill name is kebab-case (not Title Case, snake_case, camelCase)
- ✅ Folder name matches skill name
- ✅ Python files are snake_case (if present)
- Required Files:
- ✅ SKILL.md exists
- ✅ HOW_TO_USE.md exists (or usage instructions in SKILL.md)
- ✅ Python files (if skill needs code)
- ✅ sample_input.json and expected_output.json (if applicable)
- Quality:
- ✅ SKILL.md has clear capabilities section
- ✅ Input/output formats documented
- ✅ Examples provided
- ✅ No placeholder text
Output:
Validating: generated-skills/my-skill/
✅ YAML Frontmatter: Valid
✅ Skill Name: my-skill (kebab-case ✓)
✅ Required Files: All present
- SKILL.md ✓
- HOW_TO_USE.md ✓
- calculator.py ✓
- sample_input.json ✓
✅ Quality: Documentation complete
🎉 Skill validation PASSED!
Creating ZIP file for Claude Desktop...
cd generated-skills && zip -r my-skill.zip my-skill/ -x "*.pyc" "*__pycache__*" "*.DS_Store"
✅ ZIP created: generated-skills/my-skill.zip (35KB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📦 Ready to use!
**For Claude Desktop** (Easiest):
Drag and drop: generated-skills/my-skill.zip
**For Claude Code**:
/install-skill generated-skills/my-skill
Next steps:
1. Import ZIP to Claude Desktop OR install to Claude Code
2. /test-factory my-skill
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.
- 5d ago First seen · 363 lines · 0 tokens per session scan D 88563c9403de
validate-output 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,062 tokens. A static security scan graded it D with 2 findings (asks the agent to reveal its instructions, recursive force delete). 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.