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/type-strictness)<a href="https://agentmods.dev/rules/jacoby6000/smithplates/type-strictness"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/type-strictness/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/type-strictness"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/type-strictness.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.00211 | $0.00211 |
| Opus 5.5 | $0.00084 | $0.00084 |
| Sonnet 5.5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
type-strictness 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 1mo 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
Type Strictness
Build systems for typed languages or languages that support optional typing, should be configured to be as strict as possible. Any reduction in strictness must be accompanied with an explanation in the configuration.
Examples of "as strict as possible":
- TypeScript:
"strict": true(and relatednoUncheckedIndexedAccess, etc.). - Rust: deny relevant warnings (e.g.
#![deny(warnings)]/ clippy at deny). - Python: a strict type checker mode (e.g. mypy
--strict/ pyright strict).
When a strictness flag must be relaxed, document why inline in the config:
{
// DESNOTE(jbarber, 2026-06-19): noImplicitAny relaxed until the legacy
// ./vendor shims are typed; tracked in JIRA-1234.
"noImplicitAny": false
}
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.
- 1mo ago First seen · 26 lines · 211 tokens per session scan A 9e5eeefe203e
type-strictness is a cursor rule published in the GitHub repository Jacoby6000/Smithplates (2 stars, last pushed 20d ago), licensed MIT. It adds 211 tokens to every session, about $0.0008 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-09-13.
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.