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 agentmods add skills/syi0808/screenize/screenize-explorernpx skills add syi0808/screenize --skill screenize-explorergit clone --depth 1 https://github.com/syi0808/screenizeWhat 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 | $0.00034 | $0.01792 |
| Opus 5 | $0.00017 | $0.00896 |
| Sonnet 5 | $0.00007 | $0.00358 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
screenize-explorer 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 3d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Structure
MyProject.screenize/
├── project.json # ScreenizeProject v5
└── recording/
├── recording.mp4 # Video file
├── metadata.json # PolyRecordingMetadata
├── mousemoves-0.json # [PolyMouseMoveEvent]
├── mouseclicks-0.json # [PolyMouseClickEvent]
├── keystrokes-0.json # [PolyKeystrokeEvent]
└── uistates-0.json # [PolyUIStateEvent]
project.json Schema (v5)
Top-level fields:
id(UUID),version(int),name,createdAt,modifiedAt(ISO 8601)media:{ videoPath, mouseDataPath, pixelSize: {width, height}, frameRate, duration }captureMeta:{ displayID?, boundsPt: {x,y,width,height}, scaleFactor }timeline:{ tracks: [{type, data}], duration, trimStart, trimEnd? }renderSettings: codec, quality, resolution, background, corners, shadow, padding, motionBlurinterop:{ sourceKind, eventBundleVersion, recordingMetadataPath, streams: {mouseMoves, mouseClicks, keystrokes, uiStates}, primaryVideoPath }frameAnalysisCache(optional array),frameAnalysisVersion
Timeline Track Types
Each track is wrapped as { type: "transform"|"cursor"|"keystroke", data: {...} }:
Camera track (type: "transform"): segments with startTime, endTime, startTransform: {zoom, center: {x, y}}, endTransform, interpolation, mode ("manual"/"followCursor"), cursorFollow, transitionToNext
Cursor track (type: "cursor"): useSmoothCursor, segments with startTime, endTime, style, visible, scale, clickFeedback, transitionToNext
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.
- 3d ago First seen · 169 lines · 34 tokens per session scan A 2026e9555e45
screenize-explorer is a skill published in the GitHub repository syi0808/screenize (601 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,792 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…