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 serejaris/kimi-skills --skill dev-guide-generatorgit clone --depth 1 https://github.com/serejaris/kimi-skillsWrote 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/serejaris/kimi-skills/dev-guide-generator)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/dev-guide-generator"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/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.
<a href="https://agentmods.dev/skills/serejaris/kimi-skills/dev-guide-generator"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/dev-guide-generator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.02990 |
| Opus 5 | $0.00030 | $0.01495 |
| Sonnet 5 | $0.00012 | $0.00598 |
| Haiku 4.5 | $0.00006 | $0.00299 |
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 9d 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 This is a copy
100% identical to dev-guide-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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:
- Parse the topic: Identify the core technology, operational goals, and expected deliverables from the user's input
- 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?
- 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:
- 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
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.
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.
- 9d ago First seen · 379 lines · 59 tokens per session scan B ba62723b31c1
dev-guide-generator is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,990 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 100% identical to dev-guide-generator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
explain-this
Explain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a plan or findings report. Use when the user asks to "explain this", "what am I being asked", "what's happening right now", "help me understand this", "what does…
understand-change
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed"…
ape-visualize
Builds interactive, browser-based 3D Three.js visualizations of any mathematics or science concept as a single, self-contained HTML file. Takes a concept and a depth level (Simple, Intermediate, Advanced). Trigger on "ape visualize", "ape visualize math", "ape visualize science", "visualize math", "visualize science"…
ape-quiz-me
Quizzes you on content you claim to have read -- Socratic, one question at a time, hints that narrow but never reveal. Ends with a verdict on what you understood versus merely recited. Trigger on "ape quiz me", "quiz me on this", "test my understanding", "did I actually get this", or any request to be tested on shared…
ape-write-pseudocode
Guidelines for writing pseudocode for functions and algorithms. Use this skill whenever the user asks to write pseudocode, sketch out an algorithm, or describe the logic of a function at a high level. Trigger on phrases like "write pseudocode", "sketch this algorithm", "pseudocode for this function", or "describe the…