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.
git clone --depth 1 https://github.com/Jacoby6000/SmithplatesWrote 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/jacoby6000/smithplates/code-design)<a href="https://agentmods.dev/rules/jacoby6000/smithplates/code-design"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/code-design/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/rules/jacoby6000/smithplates/code-design"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/code-design.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.00641 | $0.00641 |
| Opus 5.5 | $0.00256 | $0.00256 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
code-design 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 2mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Design Principles
- Avoid global mutable state. Pass dependencies and state explicitly; no hidden singletons or shared mutable globals.
- Avoid leaky abstractions. An interface must not expose the details of its implementation (storage engine, transport, vendor SDK). Callers depend on the abstraction, never on what leaks through it.
- Favor composition over inheritance. Compose small, focused pieces; reserve inheritance for genuine substitutable is-a relationships.
- Principle of least power. Use the least powerful tool that solves the problem — prefer data over configuration, configuration over code, a pure function over a stateful object, a constant over a computation. Reach for more power only when required.
- Don't share database and transport models. Keep persistence models, API/ wire (transport) models, and domain models separate, even when they look alike. Map between them explicitly so each can evolve independently.
- Avoid private declarations. Prefer not to lock callers out. Instead of
making a declaration private, leave it accessible but document that it is not
part of the intended/stable interface — callers may have a valid, unforeseen
use case. Mark such declarations as an unstable implementation surface that
may change without notice, using the language's nearest convention (e.g. a
_-prefixed name, a#[doc(hidden)]/@internal/@unstablemarker, or an "internal — not part of the public API; subject to change" note).
Scala: nested internal object (Smithplates)
In this repository, move implementation helpers out of private into a public
nested object internal on the enclosing companion:
object SqlIrExtractor {
def extract(model: Model): SqlValidated[SqlSchema] =
model.getStructureShapes.asScala.toList
.filter(_.sqlTable.isDefined)
.traverse(internal.extractTable(_, model))
.map(internal.buildSchema)
/** Internal implementation surface — not part of the stable API; subject to change without notice. */
object internal {
def extractTable(...): SqlValidated[SqlTable] = ...
def buildSchema(...): SqlSchema = ...
}
}
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.
- 2mo ago First seen · 60 lines · 641 tokens per session scan A b237d514ec7b
code-design is a cursor rule published in the GitHub repository Jacoby6000/Smithplates (2 stars, last pushed 20d ago), licensed MIT. It adds 641 tokens to every session, about $0.0026 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-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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.