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/SecretRichGarden/metasota-API-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/secretrichgarden/metasota-api-mcp/typescript-standards)<a href="https://agentmods.dev/rules/secretrichgarden/metasota-api-mcp/typescript-standards"><img src="https://agentmods.dev/badge/rules/secretrichgarden/metasota-api-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.00000 | $0.00413 |
| Opus 5 | $0.00000 | $0.00206 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00041 |
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 8d 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 Coding Standards
Code Style
- Use strict mode TypeScript configuration
- Always use semicolons
- Use ES2022 target with Node16 module resolution
- Prefer ES Modules (
import/export) over CommonJS - Use async/await for asynchronous operations (avoid callbacks)
Type Safety
- Always define explicit types for function parameters and return values
- Use
zodschemas for runtime validation of external API responses - Avoid
anytype - useunknownif type is truly unknown, then narrow it - Use type guards and assertions when necessary
Error Handling
- Always use try-catch blocks for async operations
- Throw descriptive error messages with context
- Handle
AxiosErrorspecifically for API errors - Return error information in MCP tool responses with
isError: true
Code Organization
- Group related functionality with clear section comments (e.g.,
// ==================== 类型定义 ====================) - Keep functions focused and single-purpose
- Extract reusable logic into separate functions
- Use classes for complex stateful components (e.g.,
MetasoMCPServer)
Naming Conventions
- Use camelCase for variables and functions
- Use PascalCase for classes and types
- Use UPPER_SNAKE_CASE for constants
- Use descriptive names that indicate purpose
Example Patterns
// Good: Explicit types, error handling
async function performSearch(params: SearchParams): Promise<string> {
try {
const response = await axiosInstance.post('/search', params);
const parsed = MetasoResponseSchema.parse(response.data);
// ... process results
return formattedOutput;
} catch (error) {
if (error instanceof AxiosError) {
throw new Error(`API请求失败: ${error.response?.status}`);
}
throw error;
}
}
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.
- 8d ago First seen · 54 lines · 413 tokens per session scan A fa08621f8a60
typescript-standards is a cursor rule published in the GitHub repository SecretRichGarden/metasota-API-MCP (2 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 413 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
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.
platform-pattern-2-filesystem-operations
Cursor rule "platform-pattern-2-filesystem-operations" from PaulJPhilp/EffectPatterns, covering platform pattern 2: filesystem operations and example.
handle-unexpected-errors-by-inspecting-the-cause
Cursor rule "handle-unexpected-errors-by-inspecting-the-cause" from PaulJPhilp/EffectPatterns, covering handle unexpected errors by inspecting the cause and example.
modeling-tagged-unions-with-datacase
Cursor rule "modeling-tagged-unions-with-datacase" from PaulJPhilp/EffectPatterns, covering modeling tagged unions with data.case and example.