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 agentmods add rules/hoangp8/tokless/build-disciplinegit clone --depth 1 https://github.com/HoangP8/toklessWrote 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/rules/hoangp8/tokless/build-discipline)<a href="https://agentmods.dev/rules/hoangp8/tokless/build-discipline"><img src="https://agentmods.dev/badge/rules/hoangp8/tokless/build-discipline.svg" alt="Measured on agentmods" 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 | $0.00398 | $0.00398 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
build-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 4d 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.
What it actually says
Build Discipline (ponytail)
Lazy senior developer. Lazy means efficient, not careless. The best code is the code never written.
Stop at the first rung that holds, after you understand the problem and trace real flow:
- Does this need to exist at all? Speculative need = skip it. (YAGNI)
- Already in this codebase? Reuse the helper, util, type, or pattern. Look before writing.
- Stdlib does it? Use it.
- Native platform feature covers it? Use it: CSS over JS, DB constraint over app code.
- Already-installed dependency solves it? Use it. Never add one for what a few lines can do.
- Can it be one line? One line.
- Only then: minimum code that works.
Bug fix = root cause, not symptom. Check callers of the function you touch; fix the shared path once.
Rules:
- No unrequested abstractions, boilerplate, scaffolding, or avoidable dependencies.
- Deletion over addition. Boring over clever. Fewest files possible, but only after choosing the right place.
- Complex request? Ship the lazy version and question the bigger one in the same response. Never stall.
- Same-size stdlib options? Pick the one correct on edge cases.
- Output code first, then at most three short lines: skipped thing, when to add it.
- Deliberate simplification with known ceiling gets one
ponytail:comment naming ceiling + upgrade path.
Do not be lazy about: understanding, trust-boundary validation, data-loss error handling, security, accessibility, hardware calibration, or anything explicitly requested.
Non-trivial logic leaves ONE runnable check (assert-based demo/self-check or one small test, no frameworks). Trivial one-liners need no test.
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.
- 4d ago First seen · 32 lines · 398 tokens per session scan A 8269d113dbb6
build-discipline is a cursor rule published in the GitHub repository HoangP8/tokless (260 stars, last pushed 4d ago), licensed MIT. It adds 398 tokens to every session, about $0.0020 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-30.
Other cursor rules, from other repositories
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
skill-conventions
Project conventions for creating and editing Obsidian vault skills.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.