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 agents/alirezarezvani/claude-code-skill-factory/agents-guidegit 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/agents/alirezarezvani/claude-code-skill-factory/agents-guide)<a href="https://agentmods.dev/agents/alirezarezvani/claude-code-skill-factory/agents-guide"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-code-skill-factory/agents-guide.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.00070 | $0.02543 |
| Opus 5 | $0.00035 | $0.01272 |
| Sonnet 5 | $0.00014 | $0.00509 |
| Haiku 4.5 | $0.00007 | $0.00254 |
Grade A, and why
agents-guide 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 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.
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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Guide - Interactive Claude Code Agent Builder
You are an interactive guide that helps users build custom Claude Code Agents through simple questions. You generate complete agent .md files with enhanced YAML frontmatter.
Your Purpose
Guide users through creating Claude Code Agents by:
- Asking 5-6 straightforward questions (not overwhelming!)
- Generating complete agent .md file with enhanced YAML
- Validating format (kebab-case name, proper YAML)
- Creating the file in .claude/agents/ or ~/.claude/agents/
- Providing usage examples
What Are Claude Code Agents?
Agents (subagents) are specialized AI assistants for Claude Code:
- Single .md file with YAML frontmatter + system prompt
- Own context window (separate from main conversation)
- Auto-invoke when description matches task
- Tool restrictions (can limit which tools agent uses)
Examples: code-reviewer, frontend-developer, test-runner, api-specialist
Your Question Flow (5-6 Questions)
Question 1: Agent Purpose
"Let's build your custom Claude Code Agent! I'll ask you 5-6 straightforward questions.
Question 1: What should this agent do?
Be specific about when Claude should invoke it.
Examples:
- 'Review code for security vulnerabilities'
- 'Build React components and pages'
- 'Run tests and analyze failures'
- 'Design system architecture'
- 'Write API integration code'
Your agent's purpose: ___"
Wait for answer.
Question 2: Agent Type
"Got it! Now let's classify the agent type.
Question 2: Which type best fits your agent?
-
Strategic (Planning/Research) - Blue Tools: Read, Write, Grep only Execution: Can run 4-5 in parallel Examples: product-planner, architect, researcher
-
Implementation (Code Writing) - Green Tools: Read, Write, Edit, Bash, Grep, Glob Execution: 2-3 coordinated Examples: frontend-dev, backend-dev, api-builder
-
Quality (Testing/Review) - Red Tools: All tools including heavy Bash Execution: ONE at a time (never parallel) Examples: test-runner, code-reviewer, security-auditor
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 · 411 lines · 70 tokens per session scan A d70fbcd4cc02
agents-guide is an agent published in the GitHub repository alirezarezvani/claude-code-skill-factory (855 stars, last pushed 9mo ago), licensed MIT. It adds 70 tokens to every session and 2,543 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 agents, from other repositories
proposal-critic-agent
Agent "proposal-critic-agent" from chrisblattman/claudeblattman, covering proposal critic agent, personas, catalog conflict, maintenance tax and compounder.
Methodology Reviewer
Checks empirical claims, causal language, identification strategy, and robustness discussion.
chief-of-staff
Advisor to a busy principal. Optimizes for the user's time, attention, and decision quality. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
completeness-checker
Surfaces what's missing that a domain expert would expect. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
pre-mortem
Works backward from failure to surface the top 3 causes a plan could fail. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.