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 MithunWijayasiri/dotclaude --skill zoom-outgit clone --depth 1 https://github.com/MithunWijayasiri/dotclaudeWrote 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/mithunwijayasiri/dotclaude/zoom-out)<a href="https://agentmods.dev/skills/mithunwijayasiri/dotclaude/zoom-out"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/zoom-out/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/mithunwijayasiri/dotclaude/zoom-out"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/zoom-out.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.00039 | $0.00348 |
| Opus 5.5 | $0.00016 | $0.00139 |
| Sonnet 5.5 | $0.00008 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
zoom-out 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 19d 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.
What it actually says
Zoom Out
Create an architectural map before explaining or changing an unfamiliar code area.
Workflow
- Identify requested area and nearest entry points.
- Read relevant project instructions, glossary, architecture notes, and package configuration.
- Trace imports, callers, message or data flow, and important side effects.
- Inspect related tests and build/runtime boundaries.
- Separate verified facts from assumptions and unknowns.
- Do not edit files, run mutating commands, or propose implementation details until the map is complete.
Response
Use concise labeled sections:
- Purpose: What the area does and why it exists.
- Map: Relevant modules and responsibilities.
- Flow: Control or data movement through the area.
- Callers: Important entry points and consumers.
- Boundaries: Browser, process, API, storage, build, or module boundaries.
- Dependencies: External services, shared utilities, configuration, and contracts.
- Tests: Relevant coverage and what it verifies.
- Risks: Coupling, side effects, fragile assumptions, or likely change points.
- Unknowns: Questions the codebase does not answer.
- Summary: One short mental model of the area.
Use project glossary and established names. Cite file paths and symbols for non-obvious claims. Keep unrelated modules out of the map.
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.
- 19d ago Changed · +1 lines 855fbc9df543
- 1mo ago First seen · 40 lines · 39 tokens per session scan A d4c04b1a8c28
zoom-out is a skill published in the GitHub repository MithunWijayasiri/dotclaude (4 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 348 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
swc-plugin-compatibility
Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Vite, Rspack, or other SWC runtimes. Use when seeing errors like "failed to invoke plugin", "failed to run Wasm plugin transform", "Failed to deserialize program received from host", "Failed to execute SWC plugin", "out of bounds memory access", or…
incident-postmortem
Write a blameless post-incident review (post-mortem / RCA) that documents what happened, the timeline, root cause analysis, impact assessment, and concrete action items to prevent recurrence. Follows Google SRE blameless post-mortem culture.
troubleshooting-datavault4dbt
Diagnoses common datavault4dbt failures — satellites capturing too many or too few rows, multi-source high-water-mark issues, ghost-record/datatype errors, and YAML-metadata compile errors. Use when a datavault4dbt model errors on compile or run, a satellite detects the wrong number of changes, or a hub/link/satellite…
incident-postmortem
Use when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like "write a post-mortem", "incident review", "what went wrong", "outage report", "root cause analysis", or "RCA". Covers timeline…
code-analysis
Builds an understanding of a whole codebase or subsystem — what it does, how it is structured, where the risk and complexity concentrate, and reports it as a map someone can act on. Use this whenever the user is new to a repo, inherits unfamiliar code, asks how something works end to end, wants an architecture…
log-analysis
Extracts an answer from logs, traces, or metrics — finding the relevant lines in volume, correlating across services, and telling signal from noise. Use this whenever the user points at a log file, asks what happened at a particular time, mentions grepping logs, wants to know how often something occurs, or is trying…