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.
git clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/commands/naimkatiman/continuous-improvement/discipline)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/discipline"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/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.
<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/discipline"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/discipline.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.01085 |
| Opus 5.5 | $0.00006 | $0.00434 |
| Sonnet 5.5 | $0.00003 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The 7 Laws — Quick Reference
Print this card and check yourself against each law.
The Laws
| # | Law | Check | Red Flag |
|---|---|---|---|
| 1 | Research Before Executing | Did I search for existing solutions? | "I'll just quickly..." |
| 2 | Plan Is Sacred | Did I state WILL / WILL NOT / VERIFY? | "Let me also add..." |
| 3 | One Thing at a Time | Am I finishing before starting? | "While I'm here..." |
| 4 | Verify Before Reporting | Did I check the ACTUAL output? | "This should work..." |
| 5 | Reflect After Sessions | Did I note what worked/failed? | "I'll remember..." |
| 6 | Iterate One Change | Am I changing one thing at a time? | "And also..." |
| 7 | Learn From Every Session | Did I capture this as an instinct? | "Next time I'll..." |
Read the seven as three moments around every act. Before (Laws 1, 2): set the terms. During (Laws 3, 6): watch yourself. After (Laws 4, 5, 7): settle the account and carry it forward. Every check is an audit you run on yourself; every red flag is you hoping instead. The sentence this comes from, and its sources: docs/philosophy.md.
Operator Stakes
The Laws above are the how. These five principles are the why: code ships from your account, the incident lands on your pager, the bill hits your budget. Each one pairs with the Law that prevents it from going wrong.
| # | Principle | Vibe coder | Engineer | Law |
|---|---|---|---|---|
| 1 | Ownership | Ships auth, moves on | Adds rate limits, audit logs, password-reset flow, incident runbook before shipping | 4 |
| 2 | Reliability over cleverness | Accepts a clever regex + heavy lib that breaks on ISO 8601 with millis | Picks the boring tested API, writes tests for leap years and DST | 1 |
| 3 | Systems thinking | Builds in-memory CSV export, works for 100 dev users, OOMs in prod | Asks row count first, picks paginated background job + S3 link | 2 |
| 4 | Problem framing | Builds the websocket chat the ticket asked for | Finds out users wanted faster support replies, not chat | 1 |
| 5 | Constraints management | Calls the $0.02/image model on every upload | Does the math, adds client-side validation + caching + cheaper triage model | 2 |
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.
- 1mo ago Changed · +3 lines cde50dfccc60
- 1mo ago First seen · 66 lines · 15 tokens per session scan A cc7174fb1bf5
discipline is a command published in the GitHub repository naimkatiman/continuous-improvement (9 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,085 once invoked, about $0.0001 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.
Other commands, from other repositories
ap-swarm
Run a MultiAgentRuntime swarm in file mode — local journal at .runtime/conversation.md, no network.
reflect-promote
Promote learnings from skills to global CLAUDE.md.
reflect-meta
Show meta-learning statistics and pattern performance.
reflect-stats
Show cross-skill learning statistics.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.