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/gabriel-romero-poza/synapse-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/gabriel-romero-poza/synapse-mcp/typescript)<a href="https://agentmods.dev/rules/gabriel-romero-poza/synapse-mcp/typescript"><img src="https://agentmods.dev/badge/rules/gabriel-romero-poza/synapse-mcp/typescript.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.00239 |
| Opus 5 | $0.00000 | $0.00120 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
typescript 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 7d 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
- Strict: Respect
tsconfig.json(strict mode). Noanywithout a brief comment. - Module: ESM only (
"type": "module"). Useimport/export. - Async: Prefer
async/await; handle errors (no emptycatch). - Paths: Use
path.join()orpath.resolve()for file paths so behavior is correct on Windows and Unix. - Agnostic: No product-specific logic (no hardcoded app names, domains, or business rules in core).
Error handling:
// ❌ BAD
try {
await doSomething();
} catch (e) {}
// ✅ GOOD
try {
await doSomething();
} catch (err) {
console.error('[synapse] failed to load docs:', err);
throw err; // or return a safe default
}
Dependencies: Use pnpm. Do not add npm-specific files (e.g. package-lock.json).
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.
- 7d ago First seen · 33 lines · 0 tokens per session scan A 4b72c8bee1cf
typescript is a cursor rule published in the GitHub repository gabriel-romero-poza/synapse-mcp (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 239 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.