tech-stack

A project rule stating that the codebase uses TypeScript and Node.js version 22.

In plain words
What is it for?
Keeping generated or edited code consistent with a TypeScript project running on Node 22.
Why use it?
It tells the coding agent which programming language and runtime version to follow.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/kstrikis/ephor-mcp-collaboration/tech-stack
Clone the repo
git clone --depth 1 https://github.com/kstrikis/ephor-mcp-collaboration

Made for: Cursor.

Per session 25 This file is loaded in full into every session.
When invoked 25 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00025
Opus 5 $0.00013 $0.00013
Sonnet 5 $0.00005 $0.00005
Haiku 4.5 $0.00003 $0.00003

Measured 2d ago against content hash df799020d994, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tech-stack 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 2d 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.

Origin

This is a copy

100% identical to tech-stack — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/tech-stack.mdc · 7 lines

What it actually says

We are coding in Typescript with Node 22.

Changes

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.

  1. 2d ago First seen · 7 lines · 25 tokens per session scan A df799020d994

Subscribe to this mod's changes

tech-stack is a cursor rule published in the GitHub repository kstrikis/ephor-mcp-collaboration (1 stars, last pushed 1y ago), licensed MIT. It adds 25 tokens to every session, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tech-stack, differing in 0 lines, and is treated as a copy.