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/0ryant/engineering-doctrine/doctrine-library-changegit clone --depth 1 https://github.com/0ryant/engineering-doctrineWrote 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/0ryant/engineering-doctrine/doctrine-library-change)<a href="https://agentmods.dev/rules/0ryant/engineering-doctrine/doctrine-library-change"><img src="https://agentmods.dev/badge/rules/0ryant/engineering-doctrine/doctrine-library-change.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.1 | $0.00000 | $0.00342 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
doctrine-library-change 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 5d 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
Engineering doctrine library edits
When editing this repository’s doctrine/ tree, docs/adr/, or umbrella ENGINEERING.md:
- Follow
doctrine/patterns/doctrine-library-change-harness.md(research → ADR → layered content → navigation). - ADR: create or reference
docs/adr/; updatedocs/adr/README.mdindex for new ADRs. Skip only for pure editorial fixes. - Layering: principles vs patterns vs tooling per
doctrine/principles/timeless-principles-and-tooling.md; cross-link so there are no orphan pages. - Regenerate
doctrine/SITEMAP.md:./scripts/generate-doctrine-sitemap.sh(or./scripts/doctrine-change-preflight.sh). - Update as needed:
doctrine/glossary.md,doctrine/REFERENCES.md,doctrine/README.md,tldr-principles-and-mvp.md,ENGINEERING.md, checklists,CHANGELOG.md(material releases). - Complete
doctrine/checklists/doctrine-change-checklist.mdand state change class + consumer impact in the PR.
Use the copy-paste agent prompt in §7 of the harness file for full step-by-step tasks.
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.
- 5d ago First seen · 21 lines · 0 tokens per session scan A 8d1f2e1ec37d
doctrine-library-change is a cursor rule published in the GitHub repository 0ryant/engineering-doctrine (5 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 342 tokens. 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.