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.
npx skills add viktorbezdek/skillstack --skill coding-disciplinegit clone --depth 1 https://github.com/viktorbezdek/skillstackWrote 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/viktorbezdek/skillstack/coding-discipline)<a href="https://agentmods.dev/skills/viktorbezdek/skillstack/coding-discipline"><img src="https://agentmods.dev/badge/skills/viktorbezdek/skillstack/coding-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/viktorbezdek/skillstack/coding-discipline"><img src="https://agentmods.dev/badge/skills/viktorbezdek/skillstack/coding-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.00224 | $0.02231 |
| Opus 5.5 | $0.00090 | $0.00892 |
| Sonnet 5.5 | $0.00045 | $0.00446 |
| Haiku 4.5 | $0.00022 | $0.00223 |
Grade A, and why
coding-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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Discipline
Five empirically-grounded behavioral constraints for production LLM coding. Apply all five as a contract — not a checklist.
Principle 1 — Think Before Coding
Surface confusion. State assumptions. Take a position.
Before writing code:
- Read the relevant code first. Do not infer when you can read.
- State your top 2–3 assumptions in one line each. Proceed unless one is high-impact and uncertain.
- Ask only when (a) the request has multiple plausible interpretations AND (b) the difference is structural — changes the schema, API contract, file touched, or failure mode. Otherwise state your assumption and proceed.
- When you ask, ask once. Batch as multiple-choice (2–4 options) with a recommended default. Never ask >3 questions per turn.
Three uncertainty types — label explicitly:
| Type | Meaning | Action |
|---|---|---|
spec_uncertainty |
I don't know what you want | Ask |
code_uncertainty |
I don't know what this codebase does | Read it |
model_uncertainty |
I don't know if my approach is correct | State and verify |
Anti-patterns: menu anti-pattern · confident hallucination · sycophantic agreement · question-spam · hidden assumption
Principle 2 — Simplicity First
Smallest correct solution. Earn every abstraction. Calibrate to environment.
Defaults:
- Fewest lines that pass the acceptance criteria and survive trust-boundary inputs.
- Three duplications before an abstraction (Metz's rule). One use is not a pattern.
- Deep modules: small interfaces, rich implementations (Ousterhout). Interface complexity matters more than line count.
- Inline single-use helpers unless they hide genuine complexity or name a non-obvious operation.
Production calibration — apply when code crosses a trust boundary or runs in production:
- Validate inputs at the boundary. Not speculative — it is the boundary contract.
- Handle errors the type system cannot logically exclude. "Impossible" means logically excluded, not "I don't expect it."
- One structured log per significant branch.
- Make idempotent operations retry-safe. Make non-idempotent operations explicit.
What ships with it
3 files 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.
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 · 192 lines · 224 tokens per session scan A 212231498e0a
coding-discipline is a skill published in the GitHub repository viktorbezdek/skillstack (14 stars, last pushed 4mo ago), licensed MIT. It adds 224 tokens to every session and 2,231 once invoked, about $0.0009 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
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
api-security-best-practices
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities.
analytics-tracking
Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.
antigravity-workflows
Use when asked to ship a SaaS MVP, audit application security, build an AI agent, run browser QA, or design a domain model with multiple skills and verified checkpoints.
agent-tool-builder
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.