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-verification-gatenpx skills add mkreyman/bmad-elixir --skill elixir-verification-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-verification-gate)<a href="https://agentmods.dev/skills/mkreyman/bmad-elixir/elixir-verification-gate"><img src="https://agentmods.dev/badge/skills/mkreyman/bmad-elixir/elixir-verification-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.00039 | $0.02695 |
| Opus 5 | $0.00019 | $0.01347 |
| Sonnet 5 | $0.00008 | $0.00539 |
| Haiku 4.5 | $0.00004 | $0.00269 |
Grade B, and why
elixir-verification-gate scanned grade B 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
**Still verify.** Run `mix docs` and confirm it generates without warnings. How it starts
The opening of the file, as written. The whole thing — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elixir Verification Gate: Evidence or It Didn't Happen
THE IRON LAW
NEVER claim something works without running it and reading the output.
Not "should work". Not "looks correct". Not "I think it passes".
RUN IT. READ IT. PROVE IT.
ABSOLUTE REQUIREMENT
Before claiming ANY of the following, you MUST provide evidence:
1. "Tests pass"
MUST run: mix test
MUST read: Actual test output showing "X tests, 0 failures"
MUST provide: Exact output or test count
# Required evidence
$ mix test
..........
Finished in 0.3 seconds (0.1s async, 0.2s sync)
10 tests, 0 failures
# This is evidence ✓
2. "Code compiles"
MUST run: mix compile --warnings-as-errors
MUST read: Output showing "Compiled" or error messages
MUST provide: Confirmation of zero warnings
# Required evidence
$ mix compile --warnings-as-errors
Compiling 5 files (.ex)
Generated my_app app
# This is evidence ✓
3. "Code is formatted"
MUST run: mix format --check-formatted
MUST read: Output or lack thereof
MUST provide: Confirmation no files would be formatted
# Required evidence
$ mix format --check-formatted
# (no output means all files formatted)
# This is evidence ✓
4. "Credo passes"
MUST run: mix credo --strict
MUST read: Analysis results
MUST provide: Confirmation of "no issues found"
# Required evidence
$ mix credo --strict
Checking 42 source files...
Please report incorrect results: https://github.com/rrrene/credo/issues
Analysis took 0.3 seconds (0.2s to load, 0.1s running 100 checks on 42 files)
17 mods/funs, found no issues.
# This is evidence ✓
5. "Dialyzer passes"
MUST run: mix dialyzer
MUST read: Type checking results
MUST provide: "done (passed successfully)" message
# Required evidence
$ mix dialyzer
...
Total errors: 0, Skipped: 0, Unnecessary Skips: 0
done (passed successfully)
# This is evidence ✓
6. "Migration runs successfully"
MUST run: mix ecto.migrate
MUST read: Migration execution output
MUST provide: Confirmation migration completed
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 · 439 lines · 39 tokens per session scan B 7d3e16e252fb
elixir-verification-gate is a skill published in the GitHub repository mkreyman/bmad-elixir (10 stars, last pushed 10mo ago), licensed MIT. It adds 39 tokens to every session and 2,695 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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…