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/j-morgan6/elixir-phoenix-guide/phoenix-liveview-essentialsnpx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-liveview-essentialsgit clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guideWrote 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/j-morgan6/elixir-phoenix-guide/phoenix-liveview-essentials)<a href="https://agentmods.dev/skills/j-morgan6/elixir-phoenix-guide/phoenix-liveview-essentials"><img src="https://agentmods.dev/badge/skills/j-morgan6/elixir-phoenix-guide/phoenix-liveview-essentials.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.1 | $0.00033 | $0.02860 |
| Opus 5 | $0.00016 | $0.01430 |
| Sonnet 5 | $0.00007 | $0.00572 |
| Haiku 4.5 | $0.00003 | $0.00286 |
Grade A, and why
phoenix-liveview-essentials 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 6d 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix LiveView Essentials
RULES — Follow these with no exceptions
- Always add @impl true before every callback (mount, handle_event, handle_info, render)
- Initialize assigns before they're accessed in render/1 — use mount/3 for static defaults, handle_params/3 for URL-dependent assigns (pagination, filters, sorting)
- Check connected?(socket) before PubSub subscriptions, timers, or side effects
- Use Map.get(assigns, :key, default) for optional assigns in helper functions
- Return proper tuples —
{:ok, socket}from mount,{:noreply, socket}from handle_event - Use
withfor error handling in event handlers — assign errors to socket, don't crash auto_upload: trueworks with submit, but entries must be fully uploaded before you consume them — checkentry.done?/ rely onconsume_uploaded_entriesonly after progress completes; default to manual uploads unless you need incremental upload UX- Check
core_components.exfor existing components before creating custom ones - Never query the database directly from LiveViews — call context functions instead
Critical Concept: Two-Phase Rendering
LiveView renders happen in TWO phases:
-
Static/Disconnected Render - Initial HTTP request
- No WebSocket connection
connected?(socket)returnsfalse- Side effects (PubSub, timers) won't work
-
Connected Render - WebSocket established
- Full live functionality active
connected?(socket)returnstrue- Events and live updates work
Common Bug: Accessing uninitialized assigns during static render crashes with KeyError.
Solution: Initialize assigns before render — use mount/3 for static defaults, handle_params/3 for URL-dependent state.
LiveView Lifecycle
Mount Callback
@impl true
def mount(_params, _session, socket) do
# Initialize static defaults here; URL-dependent assigns go in handle_params
socket =
socket
|> assign(:user, nil)
|> assign(:loading, false)
|> assign(:data, [])
# Only subscribe when connected
if connected?(socket) do
Phoenix.PubSub.subscribe(MyApp.PubSub, "topic")
end
{:ok, socket}
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.
- 6d ago First seen · 445 lines · 33 tokens per session scan A d7ebddf2d6a0
phoenix-liveview-essentials is a skill published in the GitHub repository j-morgan6/elixir-phoenix-guide (160 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 2,860 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…