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 oliver-kriska/claude-elixir-phoenix --skill lv-assignsgit clone --depth 1 https://github.com/oliver-kriska/claude-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/oliver-kriska/claude-elixir-phoenix/lv-assigns)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/lv-assigns"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/lv-assigns/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/oliver-kriska/claude-elixir-phoenix/lv-assigns"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/lv-assigns.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.00047 | $0.00729 |
| Opus 5 | $0.00023 | $0.00365 |
| Sonnet 5 | $0.00009 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
lv-assigns 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 7d 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.
This is a copy
92% identical to assigns-audit — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LiveView Assigns Audit
Analyze LiveView socket assigns for memory efficiency, clarity, and best practices.
Iron Laws - Never Violate These
- Use streams for lists > 100 items - Never store large lists directly in assigns
- Use temporary_assigns for transient data - Flash messages, temp errors, notifications
- Preload only needed fields - Don't store full Ecto schemas when only needing subset
- Initialize all assigns in mount - Never access assigns that might not exist
- NEVER modify assigns or code during audit — this is a read-only diagnostic; report findings only
Quick Audit Commands
Extract All Assigns
Use Grep to find all assign( and assign_new( calls in the target LiveView file.
Find Large Data Patterns
Use Grep to find large data patterns: lists stored in assigns (assign.*\[\], assign.*Repo\.all) and full schema storage (assign.*Repo\.get) in the target file.
Audit Checklist
1. Memory Issues
| Pattern | Problem | Solution |
|---|---|---|
assign(:items, Repo.all(...)) |
Unbounded list | Use stream/3 |
assign(:user, Repo.get!(...)) |
Full schema | Select only needed fields |
assign(:file_data, binary) |
Large binary | Store reference, not data |
| Nested preloads | Excessive data | Preload only what's rendered |
2. Missing temporary_assigns
Should use temporary_assigns:
- Flash messages
- Form errors after submission
- One-time notifications
- Upload progress
def mount(_params, _session, socket) do
{:ok, socket, temporary_assigns: [flash_message: nil]}
end
3. Unused Assigns
Search for assigns defined but never used in templates:
Use Grep to extract all assign names (assign\(:(\w+)) from the LiveView file, then use Grep to find all @\w+ references in the corresponding .heex template. Compare to find unused assigns.
4. Missing Initialization
# BAD: @items might not exist
def render(assigns) do
~H"<%= for item <- @items do %>"
end
# GOOD: Initialize in mount
def mount(_params, _session, socket) do
{:ok, assign(socket, items: [])}
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.
- 7d ago First seen · 92 lines · 47 tokens per session scan A 7a757cb6513c
lv-assigns is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (542 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 729 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to assigns-audit, differing in 11 lines, and is treated as a copy.
Other skills, from other repositories
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
gurobi-advanced-features
When the user wants to use Gurobi beyond plain model building — callbacks for lazy constraints, user cuts, heuristic solution injection, and early termination; IIS computation for diagnosing an infeasible model; the solution pool; the multi-objective API; the matrix API (addMVar/addMConstr); MIP starts; and parameter…
cige-product-defect-escalation
Invoked by cige-failure-classification when a run is classified as a Product Defect: execution reached the system under test, the environment is healthy, execution steps are current — but the outcome does not match Intent.
cige-stale-execution-repair
Invoked by cige-failure-classification in two situations: Outdated Test Logic (Mode A — repair Execution[]) and a confirmed False Positive (Mode B — strengthen Guardrails). These are different repairs with different targets; do not conflate them.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.