Borrowing it
Nothing to install: this file belongs to fabioc-aloha/Alex_Skill_Mall. 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/fabioc-aloha/Alex_Skill_Mall/main/.github/instructions/lint-discipline.instructions.mdgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/instructions/fabioc-aloha/alex_skill_mall/lint-discipline)<a href="https://agentmods.dev/instructions/fabioc-aloha/alex_skill_mall/lint-discipline"><img src="https://agentmods.dev/badge/instructions/fabioc-aloha/alex_skill_mall/lint-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/instructions/fabioc-aloha/alex_skill_mall/lint-discipline"><img src="https://agentmods.dev/badge/instructions/fabioc-aloha/alex_skill_mall/lint-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.00629 | $0.00629 |
| Opus 5 | $0.00315 | $0.00315 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
Alex_Skill_Mall lint-discipline.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint Discipline
Always-on rationale: applies to any file touched in any session. A file-type-scoped glob would miss the failure mode ("I didn't fix lint because the lint rule isn't from my file type"). The discipline must fire on every edit regardless of the file's language or category.
If I edited a file, I own its lint state on exit. Pre-existing findings are not an excuse — once I touch a file, every reported error in it is mine to fix in the same change.
Rule
When get_errors (or any linter) reports problems in a file I modified this turn:
- Fix every reported error before declaring the change done.
- Do not write "pre-existing, not my edit" or "out of scope" as a reason to leave a finding.
- If a fix is genuinely risky or out of scope, name the risk and ask — do not silently ship with a disclaimer.
The user reads my touch on the file as ownership. That contract is not negotiable on a per-finding basis.
Why
Lint findings degrade silently. Each "not mine" leaves a longer tail for the next edit. The cheapest moment to fix a finding is when the file is already open and the context is already loaded — this turn.
Scope tool (VS Code 1.122+)
The search panel's "Search only in changed files" toggle restricts results to files with uncommitted SCM changes. That is exactly the scope of this rule — files I touched this turn. Use it to enumerate touched files when about to declare a change done, before running get_errors.
Anti-Patterns
| Anti-pattern | Correction |
|---|---|
| "That MD060 isn't from my edit" | Fix it. One-character delimiter spacing. |
| "Pre-existing in the file" | Pre-existing is exactly when it's cheapest to fix. |
| "Out of scope" on a one-line lint fix | Out of scope means architectural change. Lint isn't that. |
| Shipping with a disclaimer ("known issue") | Either fix it, or name the specific risk and ask. |
Trigger Origin
Burned in 2026-04-30 on a changelog edit that shipped with 10 MD060 findings called "pre-existing." User pushback: "NEVER. fix lint even if its not yours." Fixed in a follow-up commit. The follow-up should not have been needed.
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.
- 10d ago First seen · 47 lines · 629 tokens per session scan A 64cc813e6871
Alex_Skill_Mall lint-discipline.instructions.md is an instructions file published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed 3d ago), licensed MIT. It adds 629 tokens to every session, about $0.0031 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.