Borrowing it
Nothing to install: this file belongs to sachinshelke/codevira. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sachinshelke/codevira/main/.claude/skills/development-discipline/SKILL.mdgit clone --depth 1 https://github.com/sachinshelke/codeviraWrote 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/sachinshelke/codevira/development-discipline)<a href="https://agentmods.dev/skills/sachinshelke/codevira/development-discipline"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/development-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/skills/sachinshelke/codevira/development-discipline"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/development-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.00129 | $0.01551 |
| Opus 5.5 | $0.00052 | $0.00620 |
| Sonnet 5.5 | $0.00026 | $0.00310 |
| Haiku 4.5 | $0.00013 | $0.00155 |
Grade A, and why
development-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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development discipline — non-skippable sequence
When this skill triggers, you MUST complete steps 1–4 IN ORDER before calling any Edit, Write, or NotebookEdit tool. Skipping steps produces the kind of silent-failure bugs that shipped to PyPI as v2.0.0.
The 4-step sequence
Step 1 — CONTEXT (read before write)
Before any change, output:
- "I read
<file>:<lines>and the relevant code does X." - If editing: quote the exact lines being changed and what they do today.
- If creating new: list the 3 most similar existing files in the codebase that you considered.
If you haven't read the file you're about to edit, you cannot edit it. Read tool first, Edit tool second. No exceptions.
Step 2 — PURPOSE (rephrase the goal)
Output, before any code:
- "The user is asking for: ."
- "Specifically, that means: <list 1-3 concrete outcomes>."
- "It does NOT mean: ."
The "does NOT mean" line is the discipline anchor. Forces explicit scope. Without it, you'll opportunistically "improve" unrelated code and ship a 47-file PR for a 3-line bug.
Step 3 — REASON (rule out simpler paths)
Output:
- "Existing code that already does this or something close: ."
- "Approach chosen: ."
- "Approaches considered and rejected: ."
- "Files this will touch (target list): <N files, name them>."
If the touch list has >3 files, justify each one. Refactoring opportunistically beyond the touch list is out of scope. If a new file or dependency is needed, declare it here before you write it.
Step 4 — CODE (minimal diff)
Only NOW may you call Edit/Write/NotebookEdit. Constraints:
- Only modify files in the Step 3 touch list. Adding files mid-task requires re-doing Step 3.
- No "while I'm here" cleanups in unrelated files.
- No reformatting that isn't part of the change.
- No new dependencies without explicit approval.
After the change:
- Output "Test that proves the fix:
<pytest cmd or test name>." - If no test exists, write one before declaring done.
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 First seen · 174 lines · 129 tokens per session scan A e364bee43b64
development-discipline is a skill published in the GitHub repository sachinshelke/codevira (12 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 1,551 once invoked, about $0.0005 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-30.
Other skills, from other repositories
idea-to-spec
Converts vague ideas into concrete, testable specifications with acceptance criteria. No implementation begins without a spec.
ponytail-lazy-senior-dev
Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni"…
tdd-explore-ideas
Systematic codebase exploration, architectural critique, and 5-step Idea Assessment with TDD hypothesis verification for Phase 0.
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.
tdd-generate-fixtures
Generates type-safe test factories, fixtures, and seed data based on CONTEXT.md and /spec/ contracts. (Optional Utility).
project-memory-keeper
Analyzes the last session to log progress, extract lessons learned, and save them to the project memory instructions.