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/fullstack-phoenix/saas_kit/404-pagenpx skills add fullstack-phoenix/saas_kit --skill 404-pagegit clone --depth 1 https://github.com/fullstack-phoenix/saas_kitWhat 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.00040 | $0.00911 |
| Opus 5 | $0.00020 | $0.00456 |
| Sonnet 5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
404-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 yesterday.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
404 and 500 Pages
Replaces Phoenix's plain-text default error pages with branded, responsive 404
and 500 HTML templates, enables embed_templates in the ErrorHTML controller,
and adds a Fallback exception module so LiveViews can raise a 404 for missing
resources.
When to use
- The app should show styled, on-brand error pages instead of the framework defaults.
- A LiveView needs to return a real 404 when a resource isn't found, instead of
letting
Ecto.NoResultsErrorbubble up. - Don't bother if you're fine with Phoenix's built-in
"Not Found"/"Internal Server Error"plain pages.
Dependencies
- Requires: None.
- Recommended: None.
Install
mix saaskit.feature.install 404_page
No decisions to answer. The installer uncomments embed_templates in the error
controller, drops in the HEEx templates and the Fallback module, relaxes the
two error-html test assertions to regex matches, and runs mix format.
What it generates
lib/my_app_web/controllers/error_html.ex— uncommentsembed_templates "error_html/*"so the new HEEx templates are used.lib/my_app_web/controllers/error_html/404.html.heex— branded 404 page (daisyUI/Tailwind classes,gettext/1strings, link back home).lib/my_app_web/controllers/error_html/500.html.heex— branded 500 page.lib/my_app_web/fallback.ex—MyAppWeb.Fallbackexception withplug_status: 404.test/my_app_web/controllers/error_html_test.exs— assertions switched from==to=~so they tolerate the custom markup.
Configuration
No config keys are added. To preview the live pages in development, temporarily
disable debug_errors:
# config/dev.exs
config :my_app, MyAppWeb.Endpoint,
debug_errors: false
Set it back to true when you're done so you keep the dev exception trace.
Tweaking for your app
Raise a 404 from a LiveView when a record is missing:
# lib/my_app_web/live/post_live.ex
defmodule MyAppWeb.PostLive do
use MyAppWeb, :live_view
def mount(%{"id" => id}, _session, socket) do
case MyApp.Posts.get_post(id) do
nil -> raise MyAppWeb.Fallback
post -> {:ok, assign(socket, :post, post)}
end
end
end
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.
- yesterday First seen · 108 lines · 40 tokens per session scan A 1369e4970a06
404-page is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 911 once invoked, about $0.0002 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
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…