What is split-layout-technical?

A technical split-screen layout system built around two panels, thin frame lines, small metadata labels, quiet typography, and inset surfaces.

Use it for product pages, showcases, portfolios, and editorial or technical layouts that benefit from two clear desktop panels.

It gives pages with two distinct areas a consistent structure instead of treating the divider as the whole design. Each panel can have a separate role, such as focus, explanation, specifications, or navigation.

split-layout-technical — Skill for Claude Code and Codex by devinilabs

Install

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.

Any agent

npx skills add devinilabs/pro-skill --skill split-layout-technical

Clone the repo

git clone --depth 1 https://github.com/devinilabs/pro-skill

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/devinilabs/pro-skill/split-layout-technical.svg)](https://agentmods.dev/skills/devinilabs/pro-skill/split-layout-technical)

Your own site

<a href="https://agentmods.dev/skills/devinilabs/pro-skill/split-layout-technical"><img src="https://agentmods.dev/badge/skills/devinilabs/pro-skill/split-layout-technical.svg" alt="Measured on agentmods" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 810 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00032	$0.00810
Opus 5	$0.00016	$0.00405
Sonnet 5	$0.00006	$0.00162
Haiku 4.5	$0.00003	$0.00081

Measured 5d ago against content hash ae8e02a44617, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

split-layout-technical 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 5d 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.

Origin

This is a copy

100% identical to split-layout-technical — 0 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.

agent-skills/web-design/split-layout-technical/SKILL.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Split Layout Technical Skill

Use When

Create a technical split-screen design system with dual panels, fine frame lines, mono metadata, quiet editorial typography, and premium inset surfaces.

Workflow

Scope

Apply this as a full-page layout and design-system direction when the interface should be organized into two clear panels or halves.
Use it for product pages, showcases, portfolios, editorial-tech layouts, or concept presentations that benefit from a disciplined split-screen structure.
This is a layout system first: it should control framing, spacing, typography, metadata treatment, and panel behavior, not just add a vertical divider.

Visual target

Build the page around a strong split layout, usually two equal or near-equal vertical panels on desktop, with each side carrying a distinct role.
One side should act as the hero or immersive focal panel, while the other side handles explanation, specs, metadata, supporting content, or navigation.
Use thin frame lines, inset boundary rules, tiny corner markers, and precise spacing so each panel feels like a technical display surface.
Pair quiet editorial typography with mono utility labeling so the system feels intelligent, architectural, and controlled.
Keep the palette restrained, with neutral surfaces and one selective accent color derived from the design rather than a hardcoded hue.

Implementation guidance

Prefer flex-row, split columns, or a clear two-panel grid on desktop, then stack the panels vertically on smaller screens without losing the sense of separate zones.
Give each panel its own internal framing: inset vertical rules, edge offsets, corner squares, thin borders, or measured padding that creates a contained shell.
Use mono or utility text for top rails, metadata strips, labels, coordinates, system markers, specs, or status copy.
Main headlines should remain clean and confident rather than loud; support them with controlled tracking, restrained hierarchy, and generous spacing.
Feature one premium embedded surface inside at least one panel, such as a bordered media frame, canvas region, visualization area, or image window.
Let one panel feel denser and more informational while the other feels more visual, spatial, or atmospheric to create useful contrast.

Read the full file on GitHub · 53 lines

Files

What ships with it

11 files 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.

Changes

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.

5d ago First seen · 53 lines · 32 tokens per session scan A ae8e02a44617

Subscribe to this mod's changes

split-layout-technical is a skill published in the GitHub repository devinilabs/pro-skill (23 stars, last pushed 26d ago), licensed MIT. It adds 32 tokens to every session and 810 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to split-layout-technical, differing in 0 lines, and is treated as a copy.

Design and UX

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

split-layout-technical