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/abdulkader-safi/wp-to-code/porting-gotchasnpx skills add Abdulkader-Safi/wp-to-code --skill porting-gotchasgit clone --depth 1 https://github.com/Abdulkader-Safi/wp-to-codeWrote 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/abdulkader-safi/wp-to-code/porting-gotchas)<a href="https://agentmods.dev/skills/abdulkader-safi/wp-to-code/porting-gotchas"><img src="https://agentmods.dev/badge/skills/abdulkader-safi/wp-to-code/porting-gotchas.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 | $0.00082 | $0.01678 |
| Opus 5 | $0.00041 | $0.00839 |
| Sonnet 5 | $0.00016 | $0.00336 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
porting-gotchas 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 4d 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.
This is a copy
86% identical to review-architecture — 342 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Porting gotchas
Every item here cost real hours on a real port. Read them before writing markup, not after discovering one.
The rule everything else serves
Never claim a page is done without a numeric comparison, and always compare position as well as height.
Most of the bugs below pass a height check.
Layout failures that pass a height check
Margin collapse moves whole sections
A negative top margin on an inner div collapses out of its section and takes the section's background with it. The section's own height is unchanged, so height comparison sees nothing. Only position catches it.
Symptom: Δtop on one section and every section after it, with no Δh anywhere.
Fix: flow-root on the containing element. That establishes a block formatting context and stops the margin escaping.
Padding on a fixed-width box shrinks the content
w-[287px] pl-[15px] gives a 272px content box. Text rewraps, height changes, and nothing in the class list says so.
Fix: put the gap on the sibling. mr-[15px] on the icon, not pl-[15px] on the container.
Inline-block descenders
A <textarea> or <img> without display: block sits on the text baseline and adds roughly 7px of descender space below it. Enough to fail a comparison, invisible by eye.
Fix: block on the element.
Negative margins differ per page
The same component can wrap in a 558px row on one page and a 570px row on another, because the builder applied different negative margins per instance.
Do not chase this with a magic clip value. Make the row height a prop and write down why it differs.
Silent CSS failures
A missing type token emits nothing
text-28 used in three places, --text-28 never defined. Tailwind emits no rule. The element inherits its parent's size, and if it is absolutely positioned the section height stays correct.
On the port this came from, every team member's name on four pages rendered at half size for hours, through a full geometry pass.
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.
- 4d ago First seen · 125 lines · 82 tokens per session scan A 0f025fc0abb4
porting-gotchas is a skill published in the GitHub repository Abdulkader-Safi/wp-to-code (2 stars, last pushed 16d ago), licensed MIT. It adds 82 tokens to every session and 1,678 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to review-architecture, differing in 342 lines, and is treated as a copy.
Other skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
design-to-code-check
Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…
omd:showcase
Turn a rendered page (or several, side by side) into a scroll demo video — deterministic frame capture, ffmpeg H.264/GIF, labels per arm. Trigger: '시연 영상', '스크롤 영상 만들어', 'showcase', 'demo video', '비교 영상', 'record the page'.
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
s2-docs
Look up Spectrum 2 (S2) component documentation, design guidelines, and usage patterns when building with React Spectrum or Spectrum Web Components. Use when the user mentions Spectrum, S2, React Spectrum, RSP, Spectrum Web Components, or SWC, or names a Spectrum component (Button, Picker, ComboBox, TextField…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…