techContext

A project note template for recording the technologies, libraries, database, hosting, development tools, and other setup details of an application.

In plain words
What is it for?
Use it to document a project's frontend, backend, database, deployment, package manager, version control, and testing setup.
Why use it?
The provided content is only a list of fields and examples, so it does not describe an actual tool or automated behavior.

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/hansonli05/cursor-rules-system/techcontext
Clone the repo
git clone --depth 1 https://github.com/Hansonli05/Cursor-rules-system

Made for: Cursor.

Per session 1,239 This file is loaded in full into every session.
When invoked 1,239 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.01239 $0.01239
Opus 5 $0.00620 $0.00620
Sonnet 5 $0.00248 $0.00248
Haiku 4.5 $0.00124 $0.00124

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

Security

Grade A, and why

techContext 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 yesterday.

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.

.cursor/rules/memory-bank/techContext.mdc · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tech Context

Technology Stack

Frontend

  • Framework: [e.g., React, Vue, Angular, Next.js]
  • Language: [e.g., TypeScript, JavaScript]
  • Styling: [e.g., Tailwind CSS, Styled Components, CSS Modules]
  • State Management: [e.g., Redux, Zustand, Context API]
  • Build Tool: [e.g., Vite, Webpack, Next.js built-in]

Backend

  • Runtime: [e.g., Node.js, Python, Go, Java]
  • Framework: [e.g., Express, FastAPI, Gin, Spring Boot]
  • Language: [e.g., TypeScript, Python, Go, Java]
  • API Style: [e.g., REST, GraphQL, tRPC]

Database

  • Primary Database: [e.g., PostgreSQL, MongoDB, MySQL]
  • Caching: [e.g., Redis, Memcached]
  • Search: [e.g., Elasticsearch, Algolia] (if applicable)
  • File Storage: [e.g., AWS S3, Cloudinary] (if applicable)

Infrastructure & Deployment

  • Hosting: [e.g., Vercel, AWS, Google Cloud, Heroku]
  • Database Hosting: [e.g., Supabase, PlanetScale, MongoDB Atlas]
  • CDN: [e.g., Cloudflare, AWS CloudFront]
  • Monitoring: [e.g., Sentry, DataDog, New Relic]

Development Tools

  • Package Manager: [e.g., npm, yarn, pnpm]
  • Version Control: [e.g., Git, GitHub, GitLab]
  • CI/CD: [e.g., GitHub Actions, Vercel, CircleCI]
  • Code Quality: [e.g., ESLint, Prettier, Husky]
  • Testing: [e.g., Jest, Vitest, Cypress, Playwright]

Development Setup

Prerequisites

# Required software versions
Node.js: [version]
Package Manager: [npm/yarn/pnpm version]
Database: [if running locally]
Other tools: [list any other required tools]

Local Development

# Clone and setup
git clone [repository-url]
cd [project-name]
[package-manager] install

# Environment setup
cp .env.example .env.local
# [Instructions for setting up environment variables]

# Start development
[package-manager] run dev

Environment Variables

  • Required Variables:

    • DATABASE_URL: [Description]
    • API_KEY: [Description]
    • [OTHER_VAR]: [Description]
  • Optional Variables:

    • [OPTIONAL_VAR]: [Description and default]

Read the full file on GitHub · 149 lines

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. yesterday First seen · 149 lines · 1,239 tokens per session scan A bf31abaf3fcb

Subscribe to this mod's changes

techContext is a cursor rule published in the GitHub repository Hansonli05/Cursor-rules-system (2 stars, last pushed 1y ago), licensed MIT. It adds 1,239 tokens to every session, about $0.0062 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.