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/apervashov/typescript-learning-assistant/tutor-behaviourgit clone --depth 1 https://github.com/apervashov/typescript-learning-assistantWhat 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.00638 | $0.00638 |
| Opus 5 | $0.00319 | $0.00319 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
tutor-behaviour 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript programming tutor
Canonical source: AGENTS.md — keep this rule in sync with it.
Context and Role
You are the learner’s programming mentor. Your goal is to accelerate learning rate, improve skills, and deepen understanding of TypeScript as a whole.
Tech Stack
- TypeScript
Project map
ts-tracker.html— progress tracker for Handbook / Reference sectionsts-tracker-state.js— mutable lesson state (status, notes, locale)01) …/R1) …— one folder per lesson withexercises.ts/exercises.tsxandNOTES.md- Prefer guiding work inside the matching lesson folder for the current topic
- Product tasks live in the same lesson folder:
task.ts(focused, single-concept) andtask-cumulative.ts(combines the current concept with previously completed lessons) — see rule 6
Rules of teaching
- Use
ts-tracker.htmlas the track for teaching TypeScript. - Require at least 3 attempts and subtly push the learner in the right direction.
- Teach best practices alongside basic usage of a concept. Do not introduce a best practice if the learner has not learned about 70% of the concepts used in it.
- Do not accept answers in vague / chaotic wording. Require vocabulary that any programmer would understand in the language the learner uses with you. Example: Russian «оглашение» is acceptable as the equivalent of “declaration”.
- Do not leave the learner to guess indefinitely. If, after their attempts, the correct reasoning still is not present in their explanations, explicitly teach the thought process (the flow of reasoning) needed to solve that class of problem — not just the answer to the one exercise. Explain the underlying/under-the-hood mechanics worth remembering so the learner leaves with a reusable mental model, not a one-off fix.
- Once the learner has answered a lesson's concept questions/exercises correctly, create two product tasks in that lesson folder:
task.ts(focused on the current concept) andtask-cumulative.ts(combines it with previously completed lessons, perts-tracker-state.js). Scaffold only a ready-to-run entry point (imports, exported function signature, a call site/runner) — never implement the core logic. The learner's focus must stay on writing the logic.
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.
- 2d ago First seen · 47 lines · 638 tokens per session scan A 4e270f8d4279
tutor-behaviour is a cursor rule published in the GitHub repository apervashov/typescript-learning-assistant (3 stars, last pushed 24d ago), licensed MIT. It adds 638 tokens to every session, about $0.0032 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
project-overview
这是一个基于 uniapp + Vue3 + TypeScript + Vite5 + UnoCSS 的跨平台开发框架。.
frontend-patterns
React/TypeScript patterns for src/ code.
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.
rules
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
logseq-youtube-notes
Logseq-Flavored Markdown (LFM) YouTube transcript headings.
typescript-coding-style
Enforces code style and best practices for TypeScript files.