Open Steps is a collection of coding-agent skills that explain development sessions, decisions, results, and next steps in plain language. It is intended for people who use agents to build software but do not want to rely on engineering jargon, and supports Claude Code, Codex, Cursor, and Gemini CLI. The catalogue entries provide the skills, hooks, plugin, and command that make up this workflow.
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-check-workgit 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-check-work)<a href="https://agentmods.dev/skills/kharmanskyi/open-steps/os-check-work"><img src="https://agentmods.dev/badge/skills/kharmanskyi/open-steps/os-check-work/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/kharmanskyi/open-steps/os-check-work"><img src="https://agentmods.dev/badge/skills/kharmanskyi/open-steps/os-check-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 93 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00118 | $0.01861 |
| Opus 5.5 | $0.00047 | $0.00744 |
| Sonnet 5.5 | $0.00024 | $0.00372 |
| Haiku 4.5 | $0.00012 | $0.00186 |
Grade A, and why
os-check-work 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 24d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
os-check-work
You are the receiving party: another session says it finished, and your job is to find out whether that is true. Reports run optimistic - they are written by whoever did the work. Triggers live in the description above; one more is taking over work you did not do.
Language
Write in the language the user speaks in this session, detected from the conversation. Code, file names and identifiers stay English.
The stance
- A report is a claim by the party being assessed, and its adjectives are not measurements: "tests are green" vs the count that ran. Ask for the number.
- "Done" is a snapshot. Reviews get revoked, branches fall behind and checks flip, often with no new commit. Re-read immediately before you act.
Two modes
Plural is a sweep: every sibling session, one line each, statuses only.
Singular - "accept this", a named session or pull request - is an accept:
full verification, then acceptance. A sweep that finds verified-ready work
rolls into accepting it - the accept steps run first, never skipped. Where
your tool cannot list other sessions, sweep the open pull requests instead
(gh pr list) and say so.
Sweep
One line per session, one call per pull request - the reader skims these and reads the closing block. No table:
<name a person recognises (#PR)> - ; <all done? plus proof in 2-4 words, or what is missing>; <archive: yes / not yet>.
- Name from the ticket or PR title, never your shorthand; the change for the product, not a file list.
- A yes carries its proof ("checks green, review approved"); never a bare yes.
- "All done" ≠ "can archive": finished work can still await acceptance.
- Order: needs-the-user, then broken, then still-working - a running session is one word, not a finding.
- No deep verification in a sweep: say what you did not open and what that leaves unverified. Never announce your working mode - "cheap checks" is bookkeeping.
- A session waiting on an answer gets it in the same pass - see "The reply"; when that needs the deep read, the reply becomes the do-this-next.
- Name the sessions you could not read, and why.
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.
- 24d ago Changed · +2 lines 1dfe6fe86aa9
- 1mo ago First seen · 162 lines · 118 tokens per session scan A 09a7e2b5dc74
os-check-work is a skill published in the GitHub repository kharmanskyi/open-steps (1,184 stars, last pushed 20d ago), licensed MIT. It adds 118 tokens to every session and 1,861 once invoked, about $0.0005 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
travel-plan-viz
A tool that turns a travel plan into a single HTML page designed for phones and offline reading. The page can include an interactive map, a daily timeline, and reminders to book things before departure.
命理解读师
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.
learn-codebase
Socratic tutor that teaches codebase understanding through questioning, challenges, and active recall. Invoke with /learn-codebase when onboarding to a new codebase or deepening understanding of existing code. Maintains a learning journal that tracks mastery and schedules reviews.
cinematic-scroll
Design and build cinematic websites, 3D websites, interactive portfolios and product landing pages with scroll-driven storytelling, parallax, text animation and optional Three.js/WebGL scenes. Use for new experiences, motion improvements, scroll audits and storyboards in standalone HTML or an existing app. Includes…
deepread-api
Full DeepRead API reference. All endpoints, auth, request/response formats, blueprints, webhooks, error handling, and code examples for OCR, structured extraction, form filling, and PII redaction.
Linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.