elixir-discipline

elixir-discipline is a skill for Claude Code, Codex from mkreyman/bmad-elixir. It costs 38 tokens per session (1,088 once invoked), scanned A, original, MIT.

A rule set for following project-specific Elixir and Phoenix development practices. It checks which specialized guidance applies before responding or changing code.

In plain words
What is it for?
Use it as a pre-check when implementing features, debugging, reporting results, changing ignore files, or creating required data.
Why use it?
It helps prevent shortcuts such as claiming unverified results, hiding problems in configuration, or adding silent placeholder behavior.

Skill for Claude CodeCodex

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

Good fit Use it as a pre-check when implementing features, debugging, reporting results, changing ignore files, or creating required data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mkreyman/bmad-elixir/elixir-discipline
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-discipline
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-discipline

README.md
[![agentmods](https://agentmods.dev/badge/skills/mkreyman/bmad-elixir/elixir-discipline/github.svg)](https://agentmods.dev/skills/mkreyman/bmad-elixir/elixir-discipline)
Your own site
<a href="https://agentmods.dev/skills/mkreyman/bmad-elixir/elixir-discipline"><img src="https://agentmods.dev/badge/skills/mkreyman/bmad-elixir/elixir-discipline/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.

agentmods 80×15 button for elixir-discipline

Your own site · 80×15
<a href="https://agentmods.dev/skills/mkreyman/bmad-elixir/elixir-discipline"><img src="https://agentmods.dev/badge/skills/mkreyman/bmad-elixir/elixir-discipline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,088 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.00038 $0.01088
Opus 5.5 $0.00015 $0.00435
Sonnet 5.5 $0.00008 $0.00218
Haiku 4.5 $0.00004 $0.00109

Measured 2mo ago against content hash 10e90dd830cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

elixir-discipline 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 2mo 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-discipline/SKILL.md · 140 lines

How it starts

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

Elixir Discipline: Mandatory Skill Enforcement

ABSOLUTE REQUIREMENT

Before you respond to ANY request about Elixir/Phoenix code, you MUST complete this checklist.

This is NOT optional. This is NOT negotiable. You CANNOT rationalize your way out of this.

PRE-RESPONSE CHECKLIST

STOP. Before typing ANY response, ask yourself:

  1. Is this about implementing a feature or fixing a bug? → USE elixir-tdd-enforcement skill FIRST → NO CODE without failing test first

  2. Is this about debugging an error or issue? → USE elixir-root-cause-only skill → NO quick fixes, trace to root cause first

  3. Did I claim something works? → USE elixir-verification-gate skill → Run the actual command, read actual output

  4. Am I about to modify an ignore file (dialyzer.ignore, .credo.exs exclude)? → STOP IMMEDIATELY → USE elixir-no-shortcuts skill → Fix the real problem

  5. Am I creating placeholder code or default values for required data? → STOP IMMEDIATELY → USE elixir-no-placeholders skill → Fail loud, fail fast, no silent failures

  6. Am I proposing to "just try" something? → STOP → Use systematic debugging instead

IF A SKILL APPLIES, YOU MUST USE IT

This means:

  • Announce which skill you're using
  • Follow it EXACTLY
  • Do not skip steps
  • Do not modify the process

IF YOU SKIP A SKILL WHEN IT APPLIES = TASK FAILURE

RATIONALIZATIONS THAT ARE WRONG

"This is just a simple question"

WRONG. Check the skills list anyway.

"I remember this skill, I don't need to read it"

WRONG. Read it every time. The details matter.

"The skill probably doesn't apply here"

WRONG. If there's even a 1% chance it applies, you MUST read it.

"I'll just do this quickly"

WRONG. Quick usually means wrong. Use the appropriate skill.

"The user just wants a simple answer"

WRONG. The user wants a CORRECT answer. Use skills to ensure correctness.

"This would take too long"

WRONG. Doing it wrong takes longer. Use the skills.

Read the full file on GitHub · 140 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. 2mo ago First seen · 140 lines · 38 tokens per session scan A 10e90dd830cf

Subscribe to this mod's changes

elixir-discipline is a skill published in the GitHub repository mkreyman/bmad-elixir (11 stars, last pushed 1y ago), licensed MIT. It adds 38 tokens to every session and 1,088 once invoked, about $0.0002 per session on Opus 5.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

elixir-discipline compared with skills from other repositories

elixir-discipline next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
elixir-disciplinemkreyman/bmad-elixirSkill111y agoMITA38Claude Code, Codex
imagegenopenai/codexSkill135ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill395ktodayMITA36Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill80k9d agoMITA200Claude Code, Codex
next-cache-components-adoptionvercel/next.jsSkill144ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex