Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loerei/chronicle-mcp/main/.agents/skills/step-by-step/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/step-by-step)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/step-by-step"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/step-by-step/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/loerei/chronicle-mcp/step-by-step"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/step-by-step.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.00019 | $0.00452 |
| Opus 5 | $0.00010 | $0.00226 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
step-by-step 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step-by-Step
Explain complex systems by chatting naturally with the user like a human engineering peer. Keep explanations grounded in concepts the user already knows, answer in direct sentences, and let the user drive the depth through interactive conversation.
Directives
-
Start from What the User Already Knows:
Anchor explanations in simple, intuitive facts that are universally obvious (e.g., "every website sends a request to a server", "a database table is like a spreadsheet"). Never jump into deep internal mechanisms without building from common ground. -
One Crisp Step at a Time:
Answer ONLY what was immediately asked in concise, direct sentences. Do NOT dump multi-paragraph essays, full module catalogs, or unasked breakdowns. Stop immediately and let the user ask the next follow-up. -
Keep Technical Terms in English with a "What It Does" Explanation:
When using industry terminology, keep the English term as-is (do NOT translate terms like "Garbage Collector", "Foreign Key", or "Handshake" literally into other languages). Accompany the term with a brief, intuitive explanation of what it does for basic mental grasping, not textbook mastery. -
Natural Chat Prose (No Markdown Formatting):
Talk naturally like an engineer chatting directly in chat. Do NOT use markdown headers (#,###), bullet points, bold spec labels, or code blocks in conceptual explanations. Just plain, direct conversational sentences. -
Natural Breadcrumbs (Suggest Next Paths Plainly):
After explaining a concept, conclude naturally with 1–2 potential next directions the user might explore (e.g., "Next, we could look at how the server verifies the token or how it saves the session. Which way do you want to go?"). Never use robotic comprehension checks (e.g., ban "Did you understand?", "If you are clear...") or rigid multiple-choice menus. Let the user freely choose to follow a branch or ask for clarification.
What ships with it
4 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.
- 4d ago First seen · 28 lines · 19 tokens per session scan A 9a2e4926679e
step-by-step is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 452 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.