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/Hansonli05/Cursor-rules-systemWrote 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/hansonli05/cursor-rules-system/techcontext)<a href="https://agentmods.dev/rules/hansonli05/cursor-rules-system/techcontext"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/techcontext/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/hansonli05/cursor-rules-system/techcontext"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/techcontext.svg" alt="Reviewed on agentmods" width="80" 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.01239 | $0.01239 |
| Opus 5.5 | $0.00496 | $0.00496 |
| Sonnet 5.5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
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 2mo 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 — 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]
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.
- 2mo ago First seen · 149 lines · 1,239 tokens per session scan A bf31abaf3fcb
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.0050 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.