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 kharmanskyi/open-steps --skill os-step-by-stepgit clone --depth 1 https://github.com/kharmanskyi/open-stepsWrote 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/kharmanskyi/open-steps/os-step-by-step)<a href="https://agentmods.dev/skills/kharmanskyi/open-steps/os-step-by-step"><img src="https://agentmods.dev/badge/skills/kharmanskyi/open-steps/os-step-by-step.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.1 | $0.00180 | $0.01837 |
| Opus 5 | $0.00090 | $0.00919 |
| Sonnet 5 | $0.00036 | $0.00367 |
| Haiku 4.5 | $0.00018 | $0.00184 |
Grade A, and why
os-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 7d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
os-step-by-step
The user is not stuck because the task is hard - they cannot tell what they
are being asked to do. This skill turns "I need something from you" into an
instruction a person who does not read code can follow without a follow-up
question. os-done-or-not reports that something is needed; this one says
exactly how.
Language
Write in the language the user speaks in this session, detected from the conversation. Commands, file names and identifiers stay English.
When to use
Triggers live in the description above - any moment you need the user's hands, or they ask what to do.
Step 0 - earn the right to ask
Every ask costs the user a context switch. Prove it is necessary; stop at the first item that clears the block:
- Try it. A real 403 is a finding; "I probably lack permission" is a guess.
- Find another route. Another tool, a value already on the host, a file you can read.
- Shrink the ask. Obtain what you can yourself; hand over only the irreducible part.
- Check you are not asking twice - search the session and the reports folder first.
Three walls where asking IS the correct move, never to be worked around: pulling a secret into your own context, loosening a guard that is there on purpose, doing what the user said only they do.
The shape
Always this order - the ask first, never after the diagnosis.
**What I need from you: <one sentence, plain words>.**
Why you and not me: <one or two sentences. A real reason, in human terms.>
**Step 1. <action in three to six words>**
<What to do. One action only.>
**Step 2. <action>**
<...>
**How you'll know it worked.**
<What the user will see. What to do if they see something else.>
**What happens next, on my side.**
<One line: what you do once they are done, and what you will say.>
After they act - verify, do not trust
"Done" is a claim. Run the one quickest check that would fail if the step had
not worked - the file exists with the right owner, the service answers, the
value works once. Never print a secret to confirm it: confirm its effect. If
the check fails, give only the corrected step - never the whole list again.
Verified versus assumed is exactly what os-done-or-not needs for "yes"
versus "not checked".
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.
- 7d ago First seen · 161 lines · 180 tokens per session scan A 8000745ab0be
os-step-by-step is a skill published in the GitHub repository kharmanskyi/open-steps (249 stars, last pushed 3d ago), licensed MIT. It adds 180 tokens to every session and 1,837 once invoked, about $0.0009 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 skills, from other repositories
imap-client
Read, search, and download email over IMAP from the command line using the myl CLI client. Use this skill whenever the user wants to interact with their mailbox from a terminal — checking the inbox, listing or searching messages, reading a specific email, opening HTML or raw source, or saving attachments. Trigger on…
handoff-by-caio
Generates a structured Markdown handoff file to move an active conversation into a new chat, preserving full context, decisions, artifacts, and a ready-to-paste resume prompt. ALWAYS trigger this skill when the user says "move to a new chat", "move this to a new chat", "handoff", "/handoff", "continue in a new chat"…
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
manage-desktop-flows
Manage and run Power Automate Desktop (RPA) flows and machine groups. Use when the user asks about desktop flows, RPA, or machine groups.
命理解读师
A Chinese-language Zi Wei Dou Shu birth-chart interpretation guide, a form of traditional Chinese astrology based on birth details. It presents results as possible patterns rather than certain predictions and can include a chosen year's outlook.