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.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/commands/random6913/claude-code-superkit/capture-screen)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/capture-screen"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/capture-screen/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/commands/random6913/claude-code-superkit/capture-screen"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/capture-screen.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.00013 | $0.01945 |
| Opus 5.5 | $0.00005 | $0.00778 |
| Sonnet 5.5 | $0.00003 | $0.00389 |
| Haiku 4.5 | $0.00001 | $0.00194 |
Grade A, and why
capture-screen scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" "http://localhost:<PORT>" How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Screen PNG
Role
Capture a running app screen as a high-resolution PNG in public/textures/ for use as a texture on a 3D model: a full-viewport screenshot of a URL/route, or a single element marked data-screen-id (element capture runs through the Step 5 script).
Hard Rules
- Playwright CLI: use ONLY these verified flags —
--viewport-size,--device,--full-page,--wait-for-timeout. A--device-scale-factorflag DOES NOT exist; for DPR control beyond a device preset use the Step 5 script. - Dev server not responding → STOP and tell the user to start it. Never screenshot a dead server.
- No capture route found → ASK the user for the route. Never assume
/captureexists. - Defaults: iPhone 16 Pro Max — viewport 440x956, scale 2x (expected output 880x1912), corner radius R=124 (62pt × 2). Another device → use its Resolution Guide row; non-iPhone corner radius → ask the user or skip rounding, never guess.
- Before reporting done, verify the PNG's real dimensions (Step 7); if they differ from expected, report Status: MISMATCH — do not claim OK.
Prerequisites
- Dev server running (Vite, Next.js, etc.)
playwrightinstalled (npx playwright install chromium)sharpinstalled (only for rounded corners, Step 6)
Resolution Guide
| Device | Viewport | @2x Output |
|---|---|---|
| iPhone 15 Pro | 393x852 | 786x1704 |
| iPhone 16 Pro Max | 440x956 | 880x1912 |
| iPad Pro 11" | 834x1194 | 1668x2388 |
| MacBook Pro 14" | 1512x982 | 3024x1964 |
Steps
1. Resolve inputs
<PORT>= $ARGUMENTS if a port number was given, else3000. Substitute this value everywhere<PORT>appears below.- Target device: the default from Hard Rule 4, unless the user named another Resolution Guide device.
- Done when:
<PORT>, viewport, and expected output size are fixed.
2. Check dev server
curl -s -o /dev/null -w "%{http_code}" "http://localhost:<PORT>"
- Status 200–399 → continue. Anything else, or no output → STOP (Hard Rule 2): "Dev server not responding on port — start it and re-run /capture-screen."
- Done when: a 2xx/3xx status was actually observed.
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.
- 1mo ago First seen · 167 lines · 13 tokens per session scan A ce6f84e7149b
capture-screen is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 1,945 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
unity-migrate
Plan and execute Unity version or render pipeline migration — identifies deprecated APIs, package compatibility, and executes migration steps.
setup-mcp-claude-code
Build and register the Contorium MCP server for Claude Code or Cursor Agent.
orgkit-cadence
Analyze your real Claude Code usage and recommend a capture cadence + time slot, then optionally install a low-impact background batch-capture cron. Read-only analysis; the cron is opt-in.
start-session
Resume a D&D campaign session from the saved game state.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.