luongnv89/claude-howto is a visual, example-based guide to Claude Code, a coding tool that supports agents, hooks, skills, slash commands, and MCP servers. Developers use it to learn Claude Code through practical workflows and copyable templates, including the commands, agents, skills, plugins, and instructions catalogued here.
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 luongnv89/claude-howto --skill blog-draftgit clone --depth 1 https://github.com/luongnv89/claude-howtoWrote 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/luongnv89/claude-howto/blog-draft)<a href="https://agentmods.dev/skills/luongnv89/claude-howto/blog-draft"><img src="https://agentmods.dev/badge/skills/luongnv89/claude-howto/blog-draft/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.
<a href="https://agentmods.dev/skills/luongnv89/claude-howto/blog-draft"><img src="https://agentmods.dev/badge/skills/luongnv89/claude-howto/blog-draft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00047 | $0.02162 |
| Opus 5.5 | $0.00019 | $0.00865 |
| Sonnet 5.5 | $0.00009 | $0.00432 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade A, and why
blog-draft 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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- blog-draft — 91% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding. User should provide:
- Idea/Topic: The main concept or theme for the blog post
- Resources: URLs, files, or references to research (optional but recommended)
- Target audience: Who the blog post is for (optional)
- Tone/Style: Formal, casual, technical, etc. (optional)
IMPORTANT: If the user is requesting updates to an existing blog post, skip steps 0-8 and start directly at Step 9. Read the existing draft file(s) first, then proceed with the iteration process.
Execution Flow
Follow these steps sequentially. Do not skip steps or proceed without user approval where indicated.
Step 0: Create Project Folder
-
Generate a folder name using format:
YYYY-MM-DD-short-topic-name- Use today's date
- Create a short, URL-friendly slug from the topic (lowercase, hyphens, max 5 words)
-
Create the folder structure:
blog-posts/ └── YYYY-MM-DD-short-topic-name/ └── resources/ -
Confirm folder creation with user before proceeding.
Step 1: Research & Resource Collection
-
Create
resources/subfolder in the blog post directory -
For each provided resource:
- URLs: Fetch and save key information to
resources/as markdown files - Files: Read and summarize in
resources/ - Topics: Use web search to gather up-to-date information
- URLs: Fetch and save key information to
-
For each resource, create a summary file in
resources/:resources/source-1-[short-name].mdresources/source-2-[short-name].md- etc.
-
Each summary should include:
# Source: [Title/URL] ## Key Points - Point 1 - Point 2 ## Relevant Quotes/Data - Quote or statistic 1 - Quote or statistic 2 ## How This Relates to Topic Brief explanation of relevance -
Present research summary to user.
Step 2: Brainstorm & Clarify
- Based on the idea and researched resources, present:
- Main themes identified from research
- Potential angles for the blog post
- Key points that should be covered
- Gaps in information that need clarification
What ships with it
2 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.
- 1mo ago First seen · 283 lines · 47 tokens per session scan A 9b2b759fc2cb
blog-draft is a skill published in the GitHub repository luongnv89/claude-howto (41,905 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,162 once invoked, about $0.0002 per session on Opus 5.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
docs-page
A long-form technical documentation page with a left navigation panel, a main article, and a right table of contents. A table of contents lists the page sections and links to them.
how-to-tutorial-writer
Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "beginner guide to [topic]", "walkthrough for…
dg-piagent
A development guide for the pi-agent software kit, used to build and customize coding agents. It covers agents, tools, prompts, sessions, models, authentication, and connected files.
sketch-design
A small language and method for sketching how a computing operation should work before writing its implementation. It describes tensors, memory actions, loops, and optimization hints in a compact form.
triton-ascend-reduce
An optimization guide for reduction operations, which combine many values into fewer values, such as sum, mean, maximum, softmax, or normalization.
triton-ascend-matmul
An optimization guide for matrix multiplication, the operation that combines rows and columns of numbers to produce a new matrix. It explains tiling, matrix-compute cores, memory limits, alignment, and core selection on Ascend devices.