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 agentmods add skills/everywan-dev/claude-code-engineering/look-at-the-rendered-pagenpx skills add everywan-dev/claude-code-engineering --skill look-at-the-rendered-pagegit clone --depth 1 https://github.com/everywan-dev/claude-code-engineeringWrote 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/everywan-dev/claude-code-engineering/look-at-the-rendered-page)<a href="https://agentmods.dev/skills/everywan-dev/claude-code-engineering/look-at-the-rendered-page"><img src="https://agentmods.dev/badge/skills/everywan-dev/claude-code-engineering/look-at-the-rendered-page.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.00035 | $0.01695 |
| Opus 5 | $0.00017 | $0.00847 |
| Sonnet 5 | $0.00007 | $0.00339 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
look-at-the-rendered-page 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 today.
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 -H "Cookie: sessionid=<key>" https://host/the/page/ > page.html How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Look at the rendered page
The browser is the only thing that knows what the user sees.
Everything upstream of it is an opinion. The template is an opinion. The stylesheet is an opinion. The test that greps the response body for a string is an opinion about which string matters. The page is the fact.
This is the visual twin of verify-before-saying-done: that one asks for a check that could have failed; this one is about the class of web failure where every check passes and the page is still wrong.
When to use this
- You changed a template, a stylesheet, or anything that produces markup
- You are about to say a page "works", "looks right", or "is fixed"
- A test asserts a string is present — that is not the same as it being visible
- You changed a design token, a colour, or a theme
- The page needs a session, so nobody has actually opened it since the change
Why the tests keep missing it
Assertions are written to confirm something is there. The visual failures
are things that are there and wrong, or things that are there twice, or things
whose colour makes them unreadable. A test that asserts assertIn("Contract", html) passes just as happily when the button is black text on a black
background.
Four failures found in a single day on one project, none caught by a green test suite, all four obvious within two seconds of looking:
| What the tests said | What the page showed |
|---|---|
| All assertions pass | Seven lines of an internal code comment printed as body text |
| Quota renders correctly | 999 / 999 / 999, which reads as a broken panel, not "unlimited" |
| Button present with correct link | Black text on a black button — invisible in the light theme |
| Notification email delivered | The alert that was supposed to accompany it never fired |
The procedure
1. Render it. Do not reason about it. Headless Chrome is enough and is already on most machines:
chrome --headless --disable-gpu --window-size=1500,1100 \
--screenshot=out.png --virtual-time-budget=10000 \
--hide-scrollbars "file://$PWD/page.html"
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.
- today First seen · 158 lines · 35 tokens per session scan A 9e475892a8c4
look-at-the-rendered-page is a skill published in the GitHub repository everywan-dev/claude-code-engineering (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,695 once invoked, about $0.0002 per session on Opus 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-05.
Other skills, from other repositories
figma-to-webui
Recreate Figma design frames as production-ready Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines. Use when asked to create WebUI code from a Figma frame URL.
generate-token-map
Maps all Figma design tokens from figma-variables.md to their equivalent C++ (Views) identifiers, CSS (WebUI) variables, and Clank (Android) resource attributes/macros/methods in Chromium, and saves the formatted mapping table to the assets directory of the Chrome Design System project. Use this skill when asked to…
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
agent-canvas
Interactive element picker for web pages. Opens a browser with click-to-select UI overlay. Use when you need to let users visually select DOM elements, identify element selectors, or get detailed element information interactively. Triggers on "select an element", "pick element", "let me choose", "which element", or…
clone-website
Reverse-engineer and clone a website in one shot — extracts assets, CSS, and content section-by-section and proactively dispatches parallel builder agents in worktrees as it goes. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy any website. Also triggers on phrases like "make a…
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".