elixir-no-shortcuts

elixir-no-shortcuts is a skill for Claude Code, Codex from mkreyman/bmad-elixir. It costs 42 tokens per session (2,679 once invoked), scanned A, original, MIT.

A set of Elixir development rules that requires fixing the real cause of errors and warnings instead of hiding them with exclusions, disabled checks, or skipped tests.

In plain words
What is it for?
Use it when compiler, Dialyzer, Credo, test, or CI checks fail and the code or process needs a real fix.
Why use it?
It prevents quality problems from being concealed in configuration or ignored during development.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when compiler, Dialyzer, Credo, test, or CI checks fail and…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mkreyman/bmad-elixir/elixir-no-shortcuts
Install

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.

Any agent
npx skills add mkreyman/bmad-elixir --skill elixir-no-shortcuts
Clone the repo
git clone --depth 1 https://github.com/mkreyman/bmad-elixir

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for elixir-no-shortcuts

README.md
[![agentmods](https://agentmods.dev/badge/skills/mkreyman/bmad-elixir/elixir-no-shortcuts.svg)](https://agentmods.dev/skills/mkreyman/bmad-elixir/elixir-no-shortcuts)
Your own site
<a href="https://agentmods.dev/skills/mkreyman/bmad-elixir/elixir-no-shortcuts"><img src="https://agentmods.dev/badge/skills/mkreyman/bmad-elixir/elixir-no-shortcuts.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,679 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.02679
Opus 5 $0.00021 $0.01340
Sonnet 5 $0.00008 $0.00536
Haiku 4.5 $0.00004 $0.00268

Measured 6d ago against content hash 0e06941bd3f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

elixir-no-shortcuts 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.

priv/skills/elixir-no-shortcuts/SKILL.md · 343 lines

How it starts

The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Elixir No Shortcuts: Fix the Real Problem

THE IRON LAW

NEVER suppress errors. ALWAYS fix the root cause.

ABSOLUTE PROHIBITIONS

You are NEVER allowed to:

  1. Add to dialyzer.ignore

    • Not for "unknown function" errors
    • Not for "pattern can never match" warnings
    • Not for "no local return" issues
    • Not even "temporarily"
  2. Modify .credo.exs to disable checks

    • Not adding to disabled: list
    • Not adding to excluded_paths:
    • Not using inline # credo:disable-for-this-file
    • Not raising complexity limits
  3. Suppress compiler warnings

    • Not with @compile {:no_warn_undefined, Module}
    • Not with # noqa style comments
    • Not by removing --warnings-as-errors
  4. Modify .gitignore to hide problems

    • Not to hide accidentally created files
    • Not to ignore build artifacts in wrong places
    • Fix the process that created them
  5. Comment out failing tests

    • Not "just for now"
    • Not "until we figure it out"
    • Fix the test or fix the code
  6. Skip quality checks

    • Not removing from pre-commit hook
    • Not skipping with --no-verify
    • Not disabling in CI/CD

INSTEAD: FIX THE ACTUAL PROBLEM

Dialyzer Errors

When Dialyzer complains:

# BAD: Adding to dialyzer.ignore
# dialyzer.ignore
lib/my_app/accounts.ex:42:pattern_can_never_match

# GOOD: Fix with proper @spec
defmodule MyApp.Accounts do
  @spec get_user(integer()) :: {:ok, User.t()} | {:error, :not_found}
  def get_user(id) do
    case Repo.get(User, id) do
      nil -> {:error, :not_found}
      user -> {:ok, user}
    end
  end
end

Common Dialyzer fixes:

  1. Unknown function - Add @spec or import the module
  2. Pattern can never match - Fix the actual pattern mismatch
  3. No local return - Add error handling paths
  4. Invalid type specification - Correct the @spec to match reality

Process:

  1. Read the full Dialyzer error (don't just scan it)
  2. Understand what Dialyzer is telling you
  3. Add @spec that matches what the function actually does
  4. If function behavior is wrong, fix the function
  5. Run mix dialyzer again to verify

Read the full file on GitHub · 343 lines

Changes

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.

  1. 6d ago First seen · 343 lines · 42 tokens per session scan A 0e06941bd3f9

Subscribe to this mod's changes

elixir-no-shortcuts is a skill published in the GitHub repository mkreyman/bmad-elixir (10 stars, last pushed 10mo ago), licensed MIT. It adds 42 tokens to every session and 2,679 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-31.

Related

Other skills, from other repositories

dotnet-reverse

A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.

zhaoxuya520/reverse-skill · 144 tokens

check-bin-obj-clash

Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing/overwritten…

dotnet/skills · 160 tokens

dart-run-static-analysis

Execute dart analyze to identify warnings and errors, and use dart fix --apply to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.

flutter/agent-plugins · 43 tokens

hotpath_init

Configure hotpath profiling in a Rust project. Adds the hotpath dependency with feature-gated setup, instruments main with hotpath::main, functions with measure/measureall, and wraps channels, mutexes, rwlocks, streams, futures, reqwest clients, axum routers and byte-level I/O with hotpath macros. Use when the user…

pawurb/hotpath-rs · 88 tokens

agents-sdk-dotnet-debugging

Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…

microsoft/Agents · 136 tokens

golang-error-handling

Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…

samber/cc-skills-golang · 144 tokens