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 reem-sab/tech-writer-prompts --skill screenshot-to-stepsgit clone --depth 1 https://github.com/reem-sab/tech-writer-promptsWrote 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/reem-sab/tech-writer-prompts/screenshot-to-steps)<a href="https://agentmods.dev/skills/reem-sab/tech-writer-prompts/screenshot-to-steps"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/screenshot-to-steps/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/reem-sab/tech-writer-prompts/screenshot-to-steps"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/screenshot-to-steps.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.00103 | $0.00779 |
| Opus 5 | $0.00051 | $0.00390 |
| Sonnet 5 | $0.00021 | $0.00156 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
screenshot-to-steps 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 12d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenshot to Steps
Turns a numbered sequence of screenshot or screen-recording frame descriptions into a written procedure phrased by what controls are named, not where they sit or what they look like, so the steps stay accurate after the next redesign moves the button.
Inputs
{{SCREENS}}: Numbered descriptions of screenshots or recording frames, in order. Each should describe what's visible: labels, buttons, fields, and what changed from the previous frame.
How to apply
Substitute each {{PLACEHOLDER}} above with the user's actual content, then
follow the prompt below exactly — including its output format and its stated
limits.
You are converting a sequence of screen descriptions (SCREENS) into a written procedure. The procedure must still be correct after the UI is redesigned — buttons move, colors change, layouts get reorganized — as long as the underlying feature still exists. That constraint drives every phrasing choice below.
Phrasing rules
- Refer to controls by their visible text label or accessible name ("click Create API Key"), never by color, position, or size ("the blue button," "the button in the top right," "the small icon").
- If a control has no visible label in the description (an icon-only button, for example), describe it by its function instead ("the icon that opens account settings") and add it to the Fragile References list — icon-only controls are exactly the elements most likely to move or change appearance in a redesign, and function-based phrasing is the best available fallback, not a full fix.
- Describe screen locations by structural region only when necessary
(
"in the sidebar","on the Settings page"), never by pixel position ("top right","below the second card"). - Merge frames that represent a single logical action (a click and the resulting page load) into one step. Don't create a step for a frame that shows no new action, only a state change resulting from the previous step.
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.
- 12d ago First seen · 81 lines · 103 tokens per session scan A 0743f895eab2
screenshot-to-steps is a skill published in the GitHub repository reem-sab/tech-writer-prompts (4 stars, last pushed 13d ago), licensed MIT. It adds 103 tokens to every session and 779 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…