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/mkreyman/bmad-elixir/elixir-quality-gatenpx skills add mkreyman/bmad-elixir --skill elixir-quality-gategit clone --depth 1 https://github.com/mkreyman/bmad-elixirWrote 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/mkreyman/bmad-elixir/elixir-quality-gate)<a href="https://agentmods.dev/skills/mkreyman/bmad-elixir/elixir-quality-gate"><img src="https://agentmods.dev/badge/skills/mkreyman/bmad-elixir/elixir-quality-gate.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.00044 | $0.00974 |
| Opus 5 | $0.00022 | $0.00487 |
| Sonnet 5 | $0.00009 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade C, and why
elixir-quality-gate scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf _build priv/plts How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elixir Quality Gate
This skill runs comprehensive quality checks on Elixir/Phoenix projects following best practices.
When to Use
- Before creating commits
- After implementing new features
- Before merging pull requests
- When preparing for deployment
- During code reviews
Quality Checks Performed
1. Code Formatting
mix format --check-formatted
- Validates all files are properly formatted
- Fails fast if formatting issues found
- Shows which files need formatting
2. Compilation
mix compile --warnings-as-errors
- Ensures clean compilation
- Treats warnings as errors
- Catches unused variables, deprecated functions
3. Static Analysis (Credo)
mix credo --strict
- Runs strict code quality checks
- Checks for consistency, design issues, readability
- Reports refactoring opportunities
4. Type Checking (Dialyzer)
mix dialyzer
- Performs static type analysis
- Builds PLT (Persistent Lookup Table) if needed
- First run takes 1-2 minutes, subsequent runs are fast
- Catches type errors and inconsistencies
5. Test Suite
mix test
- Runs full test suite
- Reports coverage if configured
- Shows failures and pending tests
Usage Pattern
Full Quality Gate (Recommended)
Run all checks in sequence:
mix format --check-formatted && \
mix compile --warnings-as-errors && \
mix credo --strict && \
mix dialyzer && \
mix test
Quick Check (Pre-commit)
If project has a precommit alias:
mix precommit
Individual Checks
Run specific checks when iterating:
# Just format
mix format
# Just tests
mix test
# Specific test file
mix test test/my_app/accounts_test.exs
# Just credo
mix credo --strict
Error Handling
Format Failures:
- Read the output to see which files need formatting
- Run
mix formatto fix automatically - Re-run checks
Compilation Warnings:
- Read warnings carefully
- Common issues: unused variables (prefix with _), deprecated functions
- Fix warnings before proceeding
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 · 171 lines · 44 tokens per session scan C 838ec9602beb
elixir-quality-gate is a skill published in the GitHub repository mkreyman/bmad-elixir (10 stars, last pushed 10mo ago), licensed MIT. It adds 44 tokens to every session and 974 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…