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 ling-kong-ran/pisper --skill screenshot-studiogit clone --depth 1 https://github.com/ling-kong-ran/pisperWrote 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/ling-kong-ran/pisper/screenshot-studio)<a href="https://agentmods.dev/skills/ling-kong-ran/pisper/screenshot-studio"><img src="https://agentmods.dev/badge/skills/ling-kong-ran/pisper/screenshot-studio/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/ling-kong-ran/pisper/screenshot-studio"><img src="https://agentmods.dev/badge/skills/ling-kong-ran/pisper/screenshot-studio.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 Rogue Agent · line 5 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.
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.00080 | $0.01777 |
| Opus 5 | $0.00040 | $0.00889 |
| Sonnet 5 | $0.00016 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00178 |
Grade A, and why
screenshot-studio 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 5d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenshot Studio
Refresh the screenshots in docs/shots/ so the product site and README previews match the current UI. Do not change product code; only capture and replace images (and the references that name them, when needed).
When to use
Invoke only when the user explicitly asks:
/skill:screenshot-studio
This skill is for screenshot refresh work only. Do not run it during ordinary implementation or review.
Output invariants
- Every current Web screenshot PNG is exactly 2558x1380 (viewport
1279x690atdeviceScaleFactor 2); its WebP thumbnail is1600x864. - The current Web set is derived from the
shots/web/*.webpreferences indocs/index.htmlanddocs/show.html; deleted scenes are not recreated. cli.png,cli-chat.png, the mobile assets, and other non-Web/demo assets are left untouched.- No real user data, provider keys, or machine paths may appear. Use only fictional demo content and repository-relative paths.
- The isolated instance must never read the user's
~/.pisper/agentor the port-5173 dev server state.
Workflow
1. Start an isolated dev instance
node .pisper/skills/screenshot-studio/scripts/start-isolated-server.mjs --reset
This stops any prior Skill-owned process, clears only the configured screenshot agent/run directories, starts runtime/index.mjs, and waits for /api/health. Defaults are port 5180 and repository-relative directories under generated/; no project path is hard-coded.
2. Seed fictional demo data
node .pisper/skills/screenshot-studio/scripts/seed-demo-data.mjs
Creates through the real runtime APIs (never by editing the UI): six sessions, three with injected conversation transcripts, three empty; link, Markdown, and generated-image assets; a memory space with nodes; schedules; workflows (one published); and a configured OpenAI-compatible provider. Writes the created ids to generated/screenshot-run/state.json.
2b. Restart the isolated instance
What ships with it
8 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.
- references/page-map.md 3.2 KB
- scripts/browser-launch.mjs 1.1 KB runs code
- scripts/capture-screenshots.mjs 14 KB runs code
- scripts/screenshot-config.mjs 1.1 KB runs code
- scripts/seed-demo-data.mjs 17 KB runs code
- scripts/start-isolated-server.mjs 3.0 KB runs code
- scripts/verify-screenshots.mjs 2.0 KB runs code
- scripts/web-shots.mjs 859 B runs code
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.
- 5d ago Changed 261744e276c7
- 11d ago First seen · 123 lines · 80 tokens per session scan A 48fceb35215f
screenshot-studio is a skill published in the GitHub repository ling-kong-ran/pisper (285 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 1,777 once invoked, about $0.0004 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
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via…
pake
Package any website or local web build into a lightweight desktop app using Pake (Tauri/Rust). Use when the user wants to: wrap a URL as a native app, build a desktop app from a website or a local dist/ folder, use Pake CLI to package a page, set up proxy for a packaged app, customize app icons or bundle IDs, or…
remotion-animation
Generates animation configurations for Remotion including spring configs, interpolations, easing functions, and timing logic. Focuses ONLY on animation parameters, NOT component implementation. Use when defining animation behavior or when asked to "configure animations", "setup spring configs", "define easing curves".
create-remotion-geist
Create Remotion videos using the Geist design system aesthetic. Use when asked to create videos, animations, or motion graphics that should follow Vercel's visual style - dark theme, spring animations, Geist typography, and the Geist color palette.
convex-create-component
Designs and builds Convex components with isolated tables, clear boundaries, and app-facing wrappers. Use this skill when creating a new Convex component, extracting reusable backend logic into a component, building a third-party integration that owns its own tables, packaging Convex functionality for reuse, or when…
convex-quickstart
Initializes a new Convex project from scratch or adds Convex to an existing app. Use this skill when starting a new project with Convex, scaffolding with npm create convex@latest, adding Convex to an existing React, Next.js, Vue, Svelte, or other frontend, wiring up ConvexProvider, configuring environment variables…