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/aaydin-tr/swagger-navigator-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/aaydin-tr/swagger-navigator-mcp/typescript-standards)<a href="https://agentmods.dev/rules/aaydin-tr/swagger-navigator-mcp/typescript-standards"><img src="https://agentmods.dev/badge/rules/aaydin-tr/swagger-navigator-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.1 | $0.00888 | $0.00888 |
| Opus 5 | $0.00444 | $0.00444 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
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 6d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Standards
Code Quality Guidelines
- Use strict TypeScript configuration as defined in tsconfig.json
- Prefer explicit type annotations for function parameters and return values
- Use proper error handling with typed exceptions
- Implement comprehensive input validation
Module Organization
- Export functions and types explicitly
- Use clear, descriptive names for functions and variables
- Group related functionality in logical modules
- Maintain consistent import/export patterns
Type Safety
- Define interfaces for all data structures in types/
- Use discriminated unions for complex type scenarios
- Avoid
anytype - use proper type definitions - Implement type guards where necessary
Error Handling
// Good: Typed error handling
function loadConfig(): Config {
try {
// ... loading logic
} catch (error) {
if (error instanceof yaml.YAMLException) {
throw new Error(`Invalid YAML in configuration file: ${error.message}`);
}
throw error;
}
}
// Good: Input validation
function validatePath(path: string): string {
if (!path || typeof path !== "string") {
throw new Error("Invalid path provided");
}
return resolve(path);
}
Function Design
- Keep functions focused and single-purpose
- Use descriptive parameter names
- Include JSDoc comments for complex functions
- Return consistent data structures
- Handle edge cases explicitly
Import/Export Patterns
// Good: Explicit exports
export { loadConfig, detectSourceType, enrichConfigWithTypes };
// Good: Type-only imports when applicable
import type { Config, SourceConfig } from "./types/config";
import { readFileSync } from "fs";
Constants and Configuration
- Use UPPER_SNAKE_CASE for constants
- Define configuration constants at module level
- Use environment variables for runtime configuration
- Avoid magic numbers and strings
Code Documentation
- Use JSDoc for public APIs
- Include examples in documentation
- Document error scenarios
- Explain complex business logic
- Reference related modules and functions
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.
- 6d ago First seen · 168 lines · 888 tokens per session scan A d55d6f62f53a
typescript-standards is a cursor rule published in the GitHub repository aaydin-tr/swagger-navigator-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 888 tokens to every session, about $0.0044 per session on Opus 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
typescript-coding-rule
It allows a subset of JSDoc tags. Most tags must occupy their own line, with the tag at the beginning of the line.
code-style
Code style for openapi-to-cli (TypeScript).
architecture
Architecture of openapi-to-cli (ocli).
testing
Test conventions for openapi-to-cli (Jest).
global
You are an expert in Golang, TypeScript, and JavaScript development, focusing on scalable, maintainable, and performant code. Follow these principles for all suggestions, code generation, and responses.
implementation-order
Implementation order for openapi-to-cli (one unit at a time).