Better Agents is a command-line tool and set of standards for structuring, testing, evaluating, versioning, and observing AI-agent projects. It helps developers build agents with organized prompts, scenario tests, evaluation notebooks, and framework-specific guidance. Its catalogue rules guide coding assistants in applying this structure and these practices.
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/langwatch/better-agentsWrote 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/langwatch/better-agents/typescript-strict-typing)<a href="https://agentmods.dev/rules/langwatch/better-agents/typescript-strict-typing"><img src="https://agentmods.dev/badge/rules/langwatch/better-agents/typescript-strict-typing/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/langwatch/better-agents/typescript-strict-typing"><img src="https://agentmods.dev/badge/rules/langwatch/better-agents/typescript-strict-typing.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.00009 | $0.00141 |
| Opus 5.5 | $0.00004 | $0.00056 |
| Sonnet 5.5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
typescript-strict-typing 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
TypeScript Strict Typing
Never use any type. Use unknown for dynamic data, proper interfaces for complex objects, and specific union types for known value sets.
Examples:
// ❌ Bad
function processData(data: any) { ... }
const context: Record<string, any>;
// ✅ Good
type LogContext = Record<string, unknown>;
interface Config { language: string; framework: string; }
type Status = 'success' | 'error' | 'pending';
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 · 20 lines · 9 tokens per session scan A 4f9174ed3c43
typescript-strict-typing is a cursor rule published in the GitHub repository langwatch/better-agents (1,562 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 141 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
caliber-conventions
Caliber project conventions for TypeScript CLI development.
typescript-conventions
TypeScript coding conventions and style guidelines.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.
hatch3r-typescript-patterns
TypeScript and JavaScript typing mechanics — satisfies over as, discriminated unions, branded types, strict utility types, barrel exports, and import ordering.
typescript
TypeScript style rules, scoped to .ts files.
typescript
// Bad const data: any = JSON.parse(content).