building-a-discipline-spell

building-a-discipline-spell is a skill for Claude Code from redhuntlabs/wizard. It costs 37 tokens per session (1,043 once invoked), scanned A, original, MIT.

A workflow for creating a discipline spell: a saved agent rule designed to prevent a repeatedly skipped behavior.

In plain words
What is it for?
Use it to draft a `SKILL.md` containing the rule, excuses table, warning signs, and hard gates for a discipline workflow.
Why use it?
It turns a vague intention into a clear, testable rule and records the excuses or warning signs that can undermine it.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the wizard plugin — 37 skills, 6 commands, 1 agent, 1 hook shipped together

Good fit Use it to draft a SKILL.md containing the rule, excuses table, warning signs, and hard gates for a discipline workflow.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/redhuntlabs/wizard/building-a-discipline-spell
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 redhuntlabs/wizard --skill building-a-discipline-spell
Clone the repo
git clone --depth 1 https://github.com/redhuntlabs/wizard

Made for: Claude Code.

Or install wizard, the plugin that ships this one along with the rest of its 37 skills, 6 commands, 1 agent, 1 hook.

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 building-a-discipline-spell

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/redhuntlabs/wizard/building-a-discipline-spell"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/building-a-discipline-spell.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,043 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.00037 $0.01043
Opus 5 $0.00018 $0.00522
Sonnet 5 $0.00007 $0.00209
Haiku 4.5 $0.00004 $0.00104

Measured 10d ago against content hash 7b8d934447c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

building-a-discipline-spell 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 10d 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.

skills/building-a-discipline-spell/SKILL.md · 126 lines

How it starts

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

Building a Discipline Spell

What this does

Specialist builder for kind: discipline spells. A discipline is a non-negotiable rule the agent (or the user) keeps slipping on. This skill produces a SKILL.md tuned to enforce the rule against the agent's own rationalization.

When to use

  • Routed to from building-a-spell Stage 2 when kind: discipline
  • User describes a "rule I keep skipping" or "I want the AI to never do X"

What you bring (Inputs)

  • The non-negotiable rule (one sentence)
  • Why it matters (the cost of skipping)
  • The rationalizations used to skip it
  • The user's domain

What you get (Output)

A draft SKILL.md with all required discipline sections, ready for pressure-testing-a-spell to harden.

How it works (Steps)

This is a workflow chain. Stages are explicit.

Stages

Stage 1: Sharpen the rule

If the rule has any of these words, push back: "should", "try to", "consider", "when possible", "usually". A discipline rule is a hard rule.

Re-write the rule until it's:

  • One sentence
  • Imperative voice
  • Verifiable (you can tell from output whether it was followed)

Stage 2: Inventory the excuses

Ask the user (or extract from prior turns):

  • "What's the exact thing you (or the AI) tells yourself when about to skip this rule?"

Capture verbatim. Don't paraphrase. Aim for 4-6 excuses.

For each excuse, write the counter — sharp enough to actually stop the action.

Stage 3: List the warning signs

What patterns in the agent's own reasoning would predict the rule is about to break? Examples:

  • "About to claim done without verifying"
  • "About to write code without opening the test file"
  • "Reasoning includes the words 'obviously' / 'just' / 'trivially'"

These warning signs let the agent self-detect.

Stage 4: Place the hard gate

Identify the latest possible moment in the workflow where the rule could be enforced. Place a <MUST-STOP> block there with explicit "if this isn't true, STOP" language.

Discipline skills have ONE gate, placed late. Multiple gates dilute the effect.

Read the full file on GitHub · 126 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 126 lines · 37 tokens per session scan A 7b8d934447c9

Subscribe to this mod's changes

building-a-discipline-spell is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,043 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.