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 mbailey/show-me --skill look-atgit clone --depth 1 https://github.com/mbailey/show-meWrote 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/mbailey/show-me/look-at)<a href="https://agentmods.dev/skills/mbailey/show-me/look-at"><img src="https://agentmods.dev/badge/skills/mbailey/show-me/look-at.svg" alt="Measured on agentmods" 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.00034 | $0.00237 |
| Opus 5 | $0.00017 | $0.00118 |
| Sonnet 5 | $0.00007 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
look-at 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 7d 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
/show-me:look-at
Capture what the user is currently viewing with tmux hierarchy and pane content.
Targets
- (none) — Current pane content
%<id>— Specific pane by ID%1,%2,%3— Multiple paneswindow— All panes in current window
Options
-l, --lines N— Lines of scrollback-H, --hierarchy— Hierarchy only (no content)-p, --preserve-blanks— Keep exact spacing
Implementation
Run via the Bash tool. look-at is on PATH (Claude Code adds plugin bin/ to PATH automatically; for other Agent Skill runtimes, the user must put bin/look-at on PATH themselves, e.g. via a symlink into ~/.local/bin).
look-at [options] [target]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 30 lines · 34 tokens per session scan A 357317ef422b
look-at is a skill published in the GitHub repository mbailey/show-me (2 stars, last pushed 18d ago), licensed MIT. It adds 34 tokens to every session and 237 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-31.
Other skills, from other repositories
ai-web-scraping-scrapegraph
AI-powered web scraping - extract data using natural language prompts.
browser-automation-notte
Browser automation - control browser sessions, scrape pages, and run AI agents.
extract-webpage-data
Extract structured data from web pages using AI.
qp
QP (Quality Platform) router — takes a web URL or a desktop app name and runs the plan → run → regress loop (qp-plan, qp-run, qp-regress) end to end, or routes to one stage. Classifies the target (public vs profile-required), probes which adapter the session has (Playwright MCP for web, computer-use MCP for desktop)…
qp-plan
Prepare stage of QP — builds a surface inventory of a web page or desktop app (routes, menus, forms, dialogs), checks it is MECE (no overlap, nothing missing that is visible), and designs test cases as a TSV with preconditions and expected values whose SOURCE is named. Works without a spec document (then expected…
qp-run
Automation stage of QP — executes the test cases from qp-plan against the live app through the session's adapter (Playwright MCP for web, computer-use MCP for desktop), records one verdict per step with a closed status, an MTM branch, whether the step was closed by machine evidence or left to judgment, and masks…