dev-guide-generator

dev-guide-generator is a skill for Claude Code, Codex from zebbern/claude-code-guide. It costs 59 tokens per session (2,990 once invoked), scanned B, original, MIT.

A tutorial-writing workflow that turns a technical topic into a step-by-step guide, from setup and basic use through troubleshooting and advanced topics.

In plain words
What is it for?
It is for creating setup guides, quickstarts, beginner tutorials, troubleshooting sections, and final command or concept cheatsheets.
Why use it?
It helps beginners follow a clear learning path instead of piecing together instructions from scattered sources.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for creating setup guides, quickstarts, beginner tutorials, troubleshooting sections, and final command or concept cheatsheets.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zebbern/claude-code-guide/dev-guide-generator
About the project

Claude Code Guide is a reference collection for configuring and using Claude Code, Anthropic’s command-line coding agent. Developers use it to learn commands, skills, agents, MCP, automation, security, integrations, and troubleshooting. Its catalogue add-ons provide many of the documented skills and agents.

zebbern/claude-code-guide · 4,664 stars · on GitHub

Install

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.

Any agent
npx skills add zebbern/claude-code-guide --skill dev-guide-generator
Clone the repo
git clone --depth 1 https://github.com/zebbern/claude-code-guide

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dev-guide-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/zebbern/claude-code-guide/dev-guide-generator/github.svg)](https://agentmods.dev/skills/zebbern/claude-code-guide/dev-guide-generator)
Your own site
<a href="https://agentmods.dev/skills/zebbern/claude-code-guide/dev-guide-generator"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/dev-guide-generator/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.

agentmods 80×15 button for dev-guide-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/zebbern/claude-code-guide/dev-guide-generator"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/dev-guide-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,990 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 8 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Tool Misuse · line 97
    Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
    Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
  • high Tool Misuse · line 193
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Rogue Agent · line 197
    Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
    Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
  • high Tool Misuse · line 359
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Privilege Escalation · line 97
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 193
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 196
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 359
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.02990
Opus 5.5 $0.00024 $0.01196
Sonnet 5.5 $0.00012 $0.00598
Haiku 4.5 $0.00006 $0.00299

Measured 1mo ago against content hash ba62723b31c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

dev-guide-generator 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 1mo 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 for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo apt update && sudo apt install -y xxx
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/dev-guide-generator/SKILL.md · 379 lines

How it starts

The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev Guide Generator

One topic → complete technical tutorial: Through a structured SOP workflow, transform a technical topic into a comprehensive tutorial covering prerequisites, environment setup, core steps, common error troubleshooting, and advanced topics — all accompanied by a cheatsheet.

Quick Start

The user simply provides a technical topic or operational goal, and the Agent automatically generates a complete tutorial following this workflow:

User: Help me write a Docker beginner's tutorial
Agent: [Outputs complete technical tutorial + Cheatsheet following the SOP workflow]

SOP Workflow

Phase 1: Topic Scoping & Audience Analysis

Goal: Define the tutorial's technical subject, target audience, and scope boundaries.

Steps:

  1. Parse the topic: Identify the core technology, operational goals, and expected deliverables from the user's input
  2. Ask clarifying questions (up to 4 key questions):
    • What is the target audience's technical level? (Complete beginner / Some experience / Experienced developer)
    • What operating system will the reader be using? (macOS / Windows / Linux / Any)
    • What should the reader be able to do after completing the tutorial? (Specific deliverable)
    • Are there any version or tech stack constraints?
  3. If the user asks to skip clarification, proceed with these default assumptions:
    • Audience: Has basic programming experience but is unfamiliar with the topic technology
    • Environment: Cover both macOS and Linux (note Windows differences where necessary)
    • Goal: Be able to independently complete a minimal working example

Output: Tutorial metadata summary (topic, audience, objective, scope — no more than 150 words)


Phase 2: Prerequisites

Goal: List all knowledge and tools the reader needs before starting this tutorial, ensuring there are no knowledge gaps.

Steps:

  1. Dependency analysis:
    • List all technical concepts involved in this tutorial
    • For each concept, determine whether it should be "explained within the tutorial" or "assumed as prior knowledge"
    • Decision rule: If explaining it would digress more than 200 words from the main topic, classify it as a prerequisite

Read the full file on GitHub · 379 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 379 lines · 59 tokens per session scan B ba62723b31c1

Subscribe to this mod's changes

dev-guide-generator is a skill published in the GitHub repository zebbern/claude-code-guide (4,664 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 2,990 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

claude-md-coach

Reviews a learner's hand-written Claude Code setup for a level of the Agentic AI Learning Journey lab — the CLAUDE.md always, plus any skill, hook, settings.json, subagents, or MCP server the level asks them to write — identifies missing or weak elements against a rubric, challenges the learner to fix them, and…

JSchOBL/agentic-ai-learning-journey · 149 tokens

offensive-vuln-classes

Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…

SnailSploit/Claude-Red · 0 tokens

cdb-scan

Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map…

Avijit07x/claude-db · 72 tokens

algo-sensei

Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.

karanb192/algo-sensei · 51 tokens

handoff

Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…

Avijit07x/claude-db · 87 tokens

career-path-planner

Career goal mapping with skill gap analysis, actionable development plans, and milestone tracking. Use when planning career transitions, identifying skill gaps, setting professional development goals, or evaluating career options.

travisjneuman/.claude · 41 tokens