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/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-liveview-debugnpx skills add ccarvalho-eng/codex-elixir-phoenix --skill elixir-phoenix-liveview-debuggit clone --depth 1 https://github.com/ccarvalho-eng/codex-elixir-phoenixWrote 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/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-liveview-debug)<a href="https://agentmods.dev/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-liveview-debug"><img src="https://agentmods.dev/badge/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-liveview-debug.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 | $0.00023 | $0.00360 |
| Opus 5 | $0.00012 | $0.00180 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
elixir-phoenix-liveview-debug 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.
What it actually says
LiveView Debugging
Use for hard LiveView bugs: state drift, duplicate events, slow renders, reconnect inconsistencies, and stream misuse.
Iron Laws
- Reproduce first with exact event sequence and params.
- Track assign ownership by callback boundary (
mount,handle_params,handle_event,handle_info). - Verify streams for large collections before introducing list assigns.
- Distinguish transport issues from domain-state issues.
- Fix root cause, not only UI symptom.
Debug Workflow
Step 1: Build Reproduction Timeline
Capture:
- Initial mount conditions
- URL/param transitions
- User events and payloads
- Incoming PubSub/info messages
- Reconnect behavior
Step 2: Verify State Transitions
Map each callback to:
- Inputs it consumes
- Assigns it mutates
- Side effects it triggers
Look for stale assigns, overwritten state, and event-order assumptions.
Step 3: Collection and Render Checks
Audit:
- Large list assigns that should be streams
- Unbounded assign growth
- Repeated expensive computations on every render
- Temporary assigns where applicable
Step 4: Resolution Pattern
Apply the smallest safe fix:
- Move state to the correct callback boundary
- Use streams for collection updates
- Isolate side effects from render flow
- Add regression test for the exact failure timeline
Output Expectations
Return:
- Reproduction timeline
- Root-cause callback/state mismatch
- Concrete patch strategy
- Regression test scope
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 · 64 lines · 23 tokens per session scan A d1bad29214c0
elixir-phoenix-liveview-debug is a skill published in the GitHub repository ccarvalho-eng/codex-elixir-phoenix (11 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 360 once invoked, about $0.0001 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
ash-framework
Use this skill working with Ash Framework or any of its extensions. Always consult this when making any domain changes, features or fixes.
phoenix-framework
Use this skill working with Phoenix Framework. Consult this when working with the web layer, controllers, views, liveviews etc.
writing-review-packets
Create or revise Reviews packet markdown for a code diff, including section strategy, prose, hunk references, validation, and pushing packet revisions with the Reviews CLI. Use when the user asks to write a review packet, organize a diff for review, add prose around hunk refs, update a packet for a new patchset, or…
code-review
Review code changes for regressions, correctness, and missing tests.
using-reviews-locally
Run and use the Reviews app locally, including server startup, port checks, local token setup, CLI config, pushing local reviews or new patchsets, and Codex workflow conventions. Use when the user asks to spin up Reviews, push a local review packet or revision, mint/access local API tokens, debug localhost review…
reviews-overview
Explain the Reviews platform to a general agent: what Reviews provides, when to use it during human-in-the-loop or agent-driven development, how review packets structure a diff for humans, and how Reviews can precede public PR creation or integrate with other review processes. Use when an agent needs to decide whether…