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 fullstack-phoenix/saas_kit --skill layoutsgit clone --depth 1 https://github.com/fullstack-phoenix/saas_kitWrote 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/fullstack-phoenix/saas_kit/layouts)<a href="https://agentmods.dev/skills/fullstack-phoenix/saas_kit/layouts"><img src="https://agentmods.dev/badge/skills/fullstack-phoenix/saas_kit/layouts/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/fullstack-phoenix/saas_kit/layouts"><img src="https://agentmods.dev/badge/skills/fullstack-phoenix/saas_kit/layouts.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.00048 | $0.01594 |
| Opus 5.5 | $0.00019 | $0.00638 |
| Sonnet 5.5 | $0.00010 | $0.00319 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
layouts 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 2mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layouts
Replaces Phoenix's single default layout with three purpose-built layouts:
Layouts.App (authenticated app pages with sidebar nav, theme toggle, and user
menu), Layouts.Session (minimal chrome for login/registration), and
Layouts.Public (a top navbar for marketing/landing pages). It refactors the
generated layouts.ex to delegate to these modules, strips the menu out of the
root layout, and adds shared logo/1 and user_avatar/1 components. This is a
core feature most other UI builds on.
When to use
- The app has more than one kind of page — app screens behind auth, auth forms, and public pages — and each needs different chrome.
- You want a sidebar app shell, a clean session layout, and a marketing navbar out of the box, all sharing one logo and avatar.
- Don't reach for this on a single-page app where the default Phoenix layout is enough. Install it early, before features that render their own pages.
Dependencies
- Requires: None (
corefeature,position5). - Recommended: None. Pairs naturally with
authentication(the session layout wraps the login/registration/confirmation LiveViews).
Install
mix saaskit.feature.install layouts
No decisions to make — the installer generates the three layout modules, swaps
the auth LiveViews onto Layouts.Session.page, removes the nav ul from the
root layout, rewrites Layouts.app/1 to call Layouts.App.page/1, and runs
mix format.
What it generates
lib/my_app_web/components/layouts/app.ex—Layouts.App, a drawer/sidebar shell with a sticky header (theme toggle, user avatar dropdown) and anapp_nav_items/0list driving the sidebar links.lib/my_app_web/components/layouts/session.ex—Layouts.Session, a centered card with just a theme toggle, for login/registration/confirmation.lib/my_app_web/components/layouts/public.ex—Layouts.Public, a fixed top navbar with logo, nav links, and a log-in/avatar action area.lib/my_app_web/controllers/page_html/home.html.heex— a refreshed home page.- Edits
lib/my_app_web/components/layouts.ex—app/1now delegates toLayouts.App.page/1; adds sharedlogo/1anduser_avatar/1components. - Edits
lib/my_app_web/components/layouts/root.html.heex— removes the inline menu so each layout owns its own chrome. - Points the auth LiveViews (
user_live/login,registration,confirmation) atLayouts.Session.page.
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.
- 2mo ago First seen · 175 lines · 48 tokens per session scan A cfaccd38c5a2
layouts is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,594 once invoked, about $0.0002 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…