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/smithplates-build)<a href="https://agentmods.dev/rules/jacoby6000/smithplates/smithplates-build"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/smithplates-build/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/smithplates-build"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/smithplates-build.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.00936 | $0.00936 |
| Opus 5.5 | $0.00374 | $0.00374 |
| Sonnet 5.5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
smithplates-build 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smithplates Build & Toolchain
sbtn
Always use sbtn (SBT thin client) from the repository root; never run plain
sbt or coursier launch org.scala-sbt:sbt-launch:…. Assume sbtn is on
PATH (one-time install, e.g. coursier install sbtn). Do not wrap every
command with export PATH="$HOME/.local/share/coursier/bin:$PATH" or bootstrap
SBT through Coursier per invocation.
Examples: sbtn smithplatesPlugin/test, sbtn smithplatesSqlIr/test,
sbtn publishM2, sbtn scalafmtCheckAll, sbtn 'scalafixAll --check'.
sbtn is experimental — the background daemon can hang (especially after
reload, long test runs, or interrupted commands). If sbtn stops responding,
find and kill stale processes, then retry:
ps aux | rg -i 'sbtn|sbt-launch'
pkill -f 'sbtn-x86_64-pc-linux' || true
pkill -f 'sbt-launch\.jar' || true
Prefer single commands over chained sbtn 'reload; …' when possible. Use
sbtn --client shutdown only when the client still responds.
Validate
- Entry point:
./validate(default lint + test) - PR test plans should be exactly
./validateunless the user explicitly asks for a different format - Target scoping and human-oriented validate docs:
CONTRIBUTING.md
Pre-commit
After pre-commit install (see .pre-commit-config.yaml):
- Commits touching
*.scala/*.sbtrunscalafmtAll,scalafixAll, thencompileviascripts/pre-commit-scala.sh - Commits touching golden template fixtures under
templates/<language>/tests/runCodegenTemplateTestDiscoverySpec - Re-stage if fmt/fix modify sources
Scala
- Scala 3.3.6 with strict compiler options (
-Werror,-Wunused:all,-Wvalue-discard,-deprecation,-feature,-unchecked,-no-indent) - Use
{ }brace syntax only — do not use:/endoptional-brace blocks or significant-indentthen/doforms - Generic type-strictness expectations: type-strictness.mdc
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 · 81 lines · 936 tokens per session scan A 5085564fad57
smithplates-build is a cursor rule published in the GitHub repository Jacoby6000/Smithplates (2 stars, last pushed 20d ago), licensed MIT. It adds 936 tokens to every session, about $0.0037 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
python
Python best practices and patterns for modern software development with Flask and SQLite.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
rich
Definitive guidelines for building robust, maintainable, and visually appealing Python CLI applications using the rich library.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
spec-fn-naming
Spec function naming conventions.