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-whats-nextgit 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-whats-next)<a href="https://agentmods.dev/skills/kharmanskyi/open-steps/os-whats-next"><img src="https://agentmods.dev/badge/skills/kharmanskyi/open-steps/os-whats-next/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-whats-next"><img src="https://agentmods.dev/badge/skills/kharmanskyi/open-steps/os-whats-next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Rogue Agent · line 33 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 68 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.00155 | $0.01465 |
| Opus 5 | $0.00077 | $0.00732 |
| Sonnet 5 | $0.00031 | $0.00293 |
| Haiku 4.5 | $0.00015 | $0.00146 |
Grade A, and why
os-whats-next 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 10d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
os-whats-next
Answer "what do we do now" with the next move, not a map. The user does not
need the dependency graph - they need what got finished, what to take next,
and why, in plain words. This skill decides; os-step-by-step walks the user
through their part; os-done-or-not reports what came of it.
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: the description above, plus a session just ended wanting a next move.
Step 1 - read the state, quickest first
Stop as soon as you can answer.
- The last report -
~/.claude/open-steps/reports/<project>/latest.md: a handover written for exactly this moment. - Local state - uncommitted changes, unpushed commits, current branch.
- Open pull requests - one call:
gh pr list --json number,title,mergeStateStatus,reviewDecision,isDraft. - The backlog - always. The issue tracker when one is already connected
(never authenticate or install one), otherwise task files in the repo:
ROADMAP.md,PLAN.md,TODO.md,docs/plan*. Next work comes from the backlog, not from imagination. No backlog anywhere → say so.
Say which sources you did not read: an unread source is not an empty source.
Step 2 - finish what is finished
A pull request with green checks and an approval is not a decision - it is
unfinished business. Verify it through os-check-work's accept rules and
merge it in this same pass. Two things stop the merge: a failed claim, and a
task instruction that merges happen on command only - an orchestrator may own
the merge. Report it as done, never as a question.
Step 3 - sort what remains into two lists
| List | Belongs there when |
|---|---|
| I can do this alone | everything needed is at hand: no decision, no secret, no approval, no device |
| Needs you | a decision, an approval, a secret, a purchase, or a device only the user has |
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.
- 10d ago First seen · 135 lines · 155 tokens per session scan A 369405647e4d
os-whats-next is a skill published in the GitHub repository kharmanskyi/open-steps (342 stars, last pushed today), licensed MIT. It adds 155 tokens to every session and 1,465 once invoked, about $0.0008 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
命理解读师
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.
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.
cinematic-scroll
Build or improve cinematic websites with scroll-driven storytelling, pinned reveals, parallax, kinetic type, and optional 3D. Deliver standalone HTML or integrate into an existing app, with mobile and reduced-motion fallbacks and browser evidence. Also supports scroll audits and motion storyboards. Use for cinematic…
Linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
gpt-image2-ppt
A tool for creating presentation slides as high-resolution images and packaging them into a 16:9 PowerPoint file. It turns a Markdown outline or slide plan into a styled deck using OpenAI image generation.
majia-guanyuan
A practical extension layer for Guandata BI, a business-intelligence platform used to query data, build charts, and publish dashboards. It covers advanced data-pipeline work and custom HTML, CSS, and JavaScript dashboards beyond the standard tools.