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 datit309/supergraph --skill zoom-outgit clone --depth 1 https://github.com/datit309/supergraphWrote 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/datit309/supergraph/zoom-out)<a href="https://agentmods.dev/skills/datit309/supergraph/zoom-out"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/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/datit309/supergraph/zoom-out"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/zoom-out.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00460 |
| Opus 5.5 | $0.00021 | $0.00184 |
| Sonnet 5.5 | $0.00011 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
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 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.
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
/supergraph:zoom-out
One prompt. One map. Re-orient fast.
Announce: "🔭 /supergraph:zoom-out — stepping back..."
Steps
1. Read CONTEXT.md for domain vocabulary (if exists):
head -60 CONTEXT.md 2>/dev/null
2. Get architecture overview:
Use codebase-memory-mcp with CBM_PROJECT: call get_architecture for
overview, layers, boundaries, clusters, and hotspots; then use named
contract recipes hubs, bridges, and test-gaps. If unavailable, label it
unavailable and fall back to Serena/filesystem evidence.
3. Output module map using domain vocabulary from CONTEXT.md:
[Project name] — module map
[Community/Module A]
└── [file/symbol] — [one-line role in domain terms]
└── [file/symbol] — [one-line role]
[Community/Module B]
└── ...
Key flows:
[User action] → [Module A] → [Module B] → [output]
Hub nodes (high-change risk): [list]
Bridge nodes (coupling chokepoints): [list]
No implementation details. Domain language only. If a concept doesn't have a name in CONTEXT.md — use the most natural domain term and suggest adding it.
Rules
- Use domain vocabulary, not file/class names (prefer "payment processing" over "PaymentService.ts")
- If CONTEXT.md is missing or empty — use the most natural terms you can infer and note at bottom: "CONTEXT.md missing — terms inferred"
- No action items, no recommendations — orientation only
- Follow with: "Ready to /supergraph:plan, /supergraph:analyze, or /supergraph:architecture?"
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 · 52 lines · 53 tokens per session scan A 3539b1aa47ff
zoom-out is a skill published in the GitHub repository datit309/supergraph (21 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 460 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-08-30.
Other skills, from other repositories
diagnose-project
Diagnose .NET SDK, restore, build, test, package, target framework, F# compile-order, C# analyzer, and project-reference failures with concrete next checks.
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
xcode-build-run-workflow
Guide build, run, preview-adjacent, workspace-inspection, diagnostics, toolchain, and guarded mutation work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and the task is primarily about build, run, or project-integrity work rather than testing.
safari-mcp-workflow
Inspect a scoped live site in Safari through Safari Technology Preview's local MCP server. Use for Safari-specific DOM, console, network, screenshot, accessibility, performance, interaction, responsive, or print-media evidence.
xcode-debugger-mcp-workflow
Diagnose a running Apple app through Xcode’s active LLDB debugging session and assess the experimental Xcode 27 lldb-mcp executable. Use when setting breakpoints, inspecting frames or variables, issuing LLDB commands, or distinguishing a usable Xcode debugger session from an unavailable standalone debugger MCP server.