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/mrg4dget/5e-tools-mcp/typescript-standardsgit clone --depth 1 https://github.com/MrG4dget/5e-tools-mcpWrote 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/mrg4dget/5e-tools-mcp/typescript-standards)<a href="https://agentmods.dev/rules/mrg4dget/5e-tools-mcp/typescript-standards"><img src="https://agentmods.dev/badge/rules/mrg4dget/5e-tools-mcp/typescript-standards.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 | $0.00000 | $0.00102 |
| Opus 5 | $0.00000 | $0.00051 |
| Sonnet 5 | $0.00000 | $0.00020 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
typescript-standards 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 3d 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 Standards for mcp-5etools
- Enable strict mode (see tsconfig.json).
- Avoid
anyin public types; use precise interfaces and generics. - Favor small, composable functions with explicit return types for public APIs.
- Prefer pure utilities in
src/for rendering logic and tag handling. - Match existing project formatting; avoid refactors that only change formatting.
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.
- 3d ago First seen · 11 lines · 102 tokens per session scan A 55f08084a690
typescript-standards is a cursor rule published in the GitHub repository MrG4dget/5e-tools-mcp (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 102 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
docs
All documentation files use MDX format with a specific structure.
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
ts
Cursor rule "ts" from un-pany/v3-admin-vite, covering ts 开发规范, 类型, 命名, 代码组织 and 错误处理.
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.
typescript-patterns
TypeScript patterns for code organization, classes, types, and symbols as it relates to this project.
ts-inspect
Use ts-inspect for exact TypeScript semantic type information (parameters, return types, properties, signatures, definitions, type at a location) instead of reading many source files or guessing from call sites.