Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. 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/rakovi4/continue-framework/main/.claude/skills/screenshot/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/screenshot)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/screenshot"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/screenshot/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/rakovi4/continue-framework/screenshot"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/screenshot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00782 |
| Opus 5.5 | $0.00014 | $0.00313 |
| Sonnet 5.5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
screenshot 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 2mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenshot HTML Mockups
Automate taking screenshots of HTML mockups using Puppeteer from a centralized runner location.
Usage
/screenshot [folder/file]
Mockups Location
Default location: ProductSpecification/stories/*/mockups/ and ProductSpecification/stories/done/*/mockups/ — a closed story's mockups are still the design reference for the screens it owns (.claude/rules/workflow.md, "Resolving a story folder"), so a no-argument run covers both. Enumerate stories/*/mockups/ and then stories/done/*/mockups/; a single stories/*/mockups/ glob silently misses every archived story, since the archived ones sit one level deeper. Their mockups also carry a deeper <script src> prefix — .claude/templates/ui/mockup-generation-rules.md, "Script import path".
Workflow
Phase 1: Determine Scope
Parse user input to determine target:
Folder/file filtering:
/screenshot— All mockups in default location/screenshot login.html— Single file/screenshot 01_auth— Files matching pattern
Phase 2: Ensure Puppeteer Environment
The centralized Puppeteer runner is in .screenshots-temp/:
- Check if
.screenshots-temp/node_modulesexists:- If not: run
cd .screenshots-temp && npm install
- If not: run
- This only needs to happen once, not per-mockup-directory
Phase 3: Run Screenshot Script
Execute from the centralized location:
cd .screenshots-temp && node take-screenshots.js [target]
Examples:
# All mockups in default directory
cd .screenshots-temp && node take-screenshots.js
# Specific file (relative to repo root)
cd .screenshots-temp && node take-screenshots.js ../ProductSpecification/stories/01-create-task/mockups/desktop/create-task.html
# Directory with HTML files
cd .screenshots-temp && node take-screenshots.js ../ProductSpecification/stories/01-create-task/mockups/desktop/
# Filter by filename pattern
cd .screenshots-temp && node take-screenshots.js ../ProductSpecification/stories/01-create-task/mockups/ mobile
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.
- 2mo ago First seen · 92 lines · 35 tokens per session scan A 981ad8fb5a1f
screenshot is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 35 tokens to every session and 782 once invoked, about $0.0001 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…