coding-discipline

A set of guardrails for coding agents covering specification, design alignment, test-driven development, debugging, code review, verification, Git, and context management. Test-driven development means writing a failing test before the implementation.

In plain words
What is it for?
Keeping specifications and guide documents aligned, choosing checks based on risk, investigating root causes, reviewing changes by priority, verifying results with evidence, and maintaining disciplined Git history.
Why use it?
It gives agents consistent working rules and reduces errors caused by unclear intent, shallow debugging, weak verification, or stale documentation.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add chipfighter/coding-discipline
agentmods
npx agentmods add plugins/chipfighter/coding-discipline/marketplace
Clone the repo
git clone --depth 1 https://github.com/chipfighter/coding-discipline

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

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 yesterday.

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.

.claude-plugin/marketplace.json · 16 lines

What it actually says

{
  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  "name": "coding-discipline",
  "description": "Lean, firm guardrails for coding agents: spec sync plus risk-triggered design alignment, TDD, root-cause debugging, prioritized review, evidence-based verification, disciplined git, and context hygiene.",
  "owner": {
    "name": "chipfighter"
  },
  "plugins": [
    {
      "name": "coding-discipline",
      "source": "./plugins/coding-discipline",
      "description": "Eight lean but firm skills, including spec-sync for durable intent and context-hygiene against stale documentation. They trigger only when their conditions match and stay strict once active. Includes a SessionStart discipline primer, passive local usage counting, and first-entry guide-doc seeding for CLAUDE.md / AGENTS.md."
    }
  ]
}
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. yesterday First seen · 16 lines scan A 447d2ee8226e

Subscribe to this mod's changes

coding-discipline is a plugin published in the GitHub repository chipfighter/coding-discipline (6 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.