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 GabrielAmz/web-anatomy --skill build-pagegit clone --depth 1 https://github.com/GabrielAmz/web-anatomyWrote 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/gabrielamz/web-anatomy/build-page)<a href="https://agentmods.dev/skills/gabrielamz/web-anatomy/build-page"><img src="https://agentmods.dev/badge/skills/gabrielamz/web-anatomy/build-page/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/gabrielamz/web-anatomy/build-page"><img src="https://agentmods.dev/badge/skills/gabrielamz/web-anatomy/build-page.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.00181 | $0.01680 |
| Opus 5.5 | $0.00072 | $0.00672 |
| Sonnet 5.5 | $0.00036 | $0.00336 |
| Haiku 4.5 | $0.00018 | $0.00168 |
Grade A, and why
build-page 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Page
The last step of the page workflow: turn structure + copy into a wireframe someone can actually look at. write-page produces the words; build-page lays them out in a coherent design and hands the user one shareable artifact.
This is the terminal assembler. It runs on both branches:
- After a new page is written (create): assemble the chosen sections + their copy into a wireframe.
- After an existing page is improved: assemble the improved structure + copy into a shareable "here is the better version" wireframe (optional; the user can stop at the copy fixes).
It does not write copy (that is write-page), it does not diagnose (that is audit-page), and it does not invent the section list (that comes from the structure it is handed). It assembles and designs.
The one rule: a single design exemplar
A coherent page cannot be stitched from sections of different companies. Their type, color, and spacing clash, and the result reads as broken. So build-page derives the whole design system from exactly ONE source:
- Create: one exemplar homepage the user likes, picked via
find-examples/search_pages. Use it for the look only. - Improve: the user's OWN current page. It already has a coherent design language; keep it and re-skin the improved structure + copy in it.
The exemplar drives DESIGN only: type scale, color direction, spacing rhythm, component style, section layout patterns. Never lift the exemplar's words, claims, or brand name. The copy is the user's, from write-page.
Step 0 - Gather the inputs
build-page needs two things. Do not start without both:
- Structure + copy. Prefer the most recent
write-pageoutput for this page (.webanatomy/write-page/{page}-*/report-data.jsonand itsrecommendations/ written sections). If the user is runningbuild-pagedirectly without a priorwrite-pagerun, ask them to runwrite-pagefirst (build or improve mode); this skill assembles, it does not generate the copy. - One design exemplar.
- Create: ask which exemplar homepage to follow, or surface candidates via
find-examplesand let the user pick one. Capture its screenshot as the design reference. - Improve: use the current page already captured by
audit-page/write-page(references/current.png). If none exists, capture it now.
- Create: ask which exemplar homepage to follow, or surface candidates via
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 · 89 lines · 181 tokens per session scan A 527f6eca2d7a
build-page is a skill published in the GitHub repository GabrielAmz/web-anatomy (11 stars, last pushed 3mo ago), licensed MIT. It adds 181 tokens to every session and 1,680 once invoked, about $0.0007 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-31.
Other skills, from other repositories
mobile-responsive
Mobile-first responsive design patterns for sales funnels. Ensures every page works flawlessly on all screen sizes with proper touch targets, readable typography, and fast load times.
animejs-animation
Advanced JavaScript animation library skill for creating complex, high-performance web animations.
antigravity-design-expert
Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.