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/maludb-ed/htmx-php-builder/new-screennpx skills add maludb-ed/htmx-php-builder --skill new-screengit clone --depth 1 https://github.com/maludb-ed/htmx-php-builderWhat 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.00081 | $0.00876 |
| Opus 5 | $0.00041 | $0.00438 |
| Sonnet 5 | $0.00016 | $0.00175 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
new-screen 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 3d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Screen Workflow
Every screen must be indistinguishable in style from the rest of the application. Never design a screen from scratch — assemble it from the canonical patterns.
Steps
- Read the design system first. Open the design-system skill's references —
design-decisions.mdfirst (it overrides everything), thenlayout-skeleton.html/components.md, and start from the matching page inexamples/:- List screen → the canonical "Traffic Reports" table card with server-rendered pagination (
examples/partials/customers-list.html) - Detail screen → view/panels pattern (
examples/partials/customer-view.html) - Create/edit → full-container form partial (
examples/partials/customer-form.html) - Auth-related → minimal auth layout (
examples/auth-login.html)
- List screen → the canonical "Traffic Reports" table card with server-rendered pagination (
- Follow the php-patterns skill for the file layout and handler structure: endpoints under
/var/www/html/{feature}/(the Apache DocumentRoot) (index.php,form.php,save.php,delete.php), query functions inapp/features/{feature}/queries.php, views underapp/views/{feature}/(page.php+partials/). One screen = the pattern's prescribed files, no more. - HTMX wiring. The screen renders as a partial into the shell's main content target (see the marked
MAIN CONTENT TARGETcomment in the layout skeleton). Navigation links usehx-get+hx-push-urlwith an explicit canonical URL —hx-push-url="true"is banned (it pushes the partial's path and breaks relative URLs); forms usehx-postreturning either the updated partial or anHX-Redirectheader. The page must also render standalone (full layout) when requested directly, so deep links and refreshes work. - Interaction rules (no modals) — the CRUD contract:
- Every list screen: "Add " primary button in the page-header actions + an explicit Edit button on every table row; both
hx-getthe same full-container form partial (empty vs pre-filled) into the shell swap target withhx-push-url. - Create/edit/detail: dedicated full pages.
- Quick single-field edits: inline HTMX swap in place.
- Filters or quick previews only: offcanvas drawer, full-width on mobile. Never put a form submit inside an offcanvas.
- Confirmations:
hx-confirmon the destructive control (the no-modal rule covers forms and display pages, not confirmations).
- Every list screen: "Add " primary button in the page-header actions + an explicit Edit button on every table row; both
- Activity logging. The handler logs screen entry and every state-changing action to the activity log.
- Mobile check before done. Verify at 375px: no horizontal scroll, tables wrap in
.table-responsive, toolbars stack, touch targets ≥ 44px. A screen is not finished until this passes. - Register it. Add the sidebar/menu entry using the exact menu-item markup from the layout skeleton.
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.
- 3d ago First seen · 35 lines · 81 tokens per session scan A 68fed7a3125a
new-screen is a skill published in the GitHub repository maludb-ed/htmx-php-builder (8 stars, last pushed 27d ago), licensed MIT. It adds 81 tokens to every session and 876 once invoked, about $0.0004 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…