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 Justinmendezai/The-Adam-Repo --skill zoom-outgit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/zoom-out)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/zoom-out"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/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/justinmendezai/the-adam-repo/zoom-out"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/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.00054 | $0.00503 |
| Opus 5 | $0.00027 | $0.00251 |
| Sonnet 5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
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 12d 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
Adapted from Matt Pocock's zoom-out. Before you make a change, understand what it's part of.
When to use
- You're about to modify a function in a module you've never read before.
- The user pastes a snippet and asks "what does this do?" — answer the system-level question, not just line-by-line.
- You suspect the change is bigger than the user thinks.
Workflow
For a target file/function:
- Read its module's entry point (often
index.ts,mod.rs, or the file's containing module). Note what it exports. - Find its callers. Use the
code-review-graphMCP if available, orGrepfor imports of the symbol. List file:line for each caller. - Find its dependencies. What does it import? Are those internal or third-party?
- Place it in the architecture. Read
plan/CONTEXT.md(ordocs/) and locate the file's module in the system diagram. - Identify invariants. What's the function's contract? What does its docstring say? What do its tests prove?
- Now answer. A good answer has three parts:
- Purpose: what this exists to do, in one sentence.
- Context: where it sits in the system (the module it's part of, the callers it serves).
- Constraints: invariants the change must preserve.
Output shape
Three short paragraphs, in that order. Then — only then — answer the original question or proceed with the change.
Anti-patterns
- Reading the function in isolation. You'll miss the contract.
- Listing every caller without reading any of them. The number isn't useful; the patterns are.
- "I'll just trace through it" without writing the answer down. The agent's next session won't have your trace.
Output
A three-paragraph zoom-out, suitable for inclusion in a PR description or a CONTEXT.md update.
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.
- 12d ago First seen · 43 lines · 54 tokens per session scan A a64409bb1db1
zoom-out is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 54 tokens to every session and 503 once invoked, about $0.0003 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.