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/activecontext)<a href="https://agentmods.dev/rules/hansonli05/cursor-rules-system/activecontext"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/activecontext/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/activecontext"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/activecontext.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.00501 | $0.00501 |
| Opus 5.5 | $0.00200 | $0.00200 |
| Sonnet 5.5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
activeContext 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.
What it actually says
Active Context
Current Sprint Goal
[GOAL] [Sprint Name] - [Primary objective for current development cycle]
Session Focus
[IN_PROGRESS] Current Session - [What are you working on right now?]
Recent Changes (Last 7 Days)
- [COMPLETE] [Feature/Change 1] - [Brief description]
- [COMPLETE] [Feature/Change 2] - [Brief description]
- [IN_PROGRESS] [Feature/Change 3] - [Current status]
Immediate Next Steps
- [PRIORITY] [Next Action 1] - [Description and context]
- [READY] [Next Action 2] - [Description and context]
- [BLOCKED] [Next Action 3] - [Description and blocker]
Active Decisions/Considerations
- [DECISION] [Decision Topic 1] - [What needs to be decided and why]
- [RISK] [Risk/Concern 1] - [Description and potential impact]
- [DEPENDENCY] [Dependency 1] - [What you're waiting on]
Current Technical Focus
- [TECH] Primary Technology: [What you're implementing with]
- [TECH] Integration Points: [Key systems being connected]
- [TECH] Performance Considerations: [Current optimization focus]
Team Context (if applicable)
- [TEAM] Collaboration Points: [Who you're working with on what]
- [TEAM] Handoffs: [What's being passed between team members]
- [TEAM] Reviews: [Code reviews, design reviews in progress]
Context for AI
- Feature Domain: [Which feature-rules/*.mdc files are most relevant]
- Technical Domain: [Which tech-stack/*.mdc files are most relevant]
- Architectural Concerns: [Key patterns from systemPatterns.mdc to consider]
Questions/Clarifications Needed
- [Question 1]: [What needs clarification and why]
- [Question 2]: [What needs clarification and why]
Update Frequency: This file should be updated at the start and end of each development session to maintain current context.
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 · 51 lines · 501 tokens per session scan A 3f93690396c4
activeContext is a cursor rule published in the GitHub repository Hansonli05/Cursor-rules-system (2 stars, last pushed 1y ago), licensed MIT. It adds 501 tokens to every session, about $0.0020 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
project-memory
This rule guides recording project events and decisions in projectmem.
decision-logger
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting…
team-brain
Team Brain sync mode — one start per ticket, then live merge-safe crew memory. Always-on when .team-brain exists or work mentions an initiative/Jira key.
swamr-obsidian-brain
Swamr Obsidian Brain — persistent knowledge base that agents read from and write to across phases. Prevents context loss by maintaining architecture decisions, task outputs, learned patterns, and project knowledge in an Obsidian vault. Every agent MUST read relevant notes before starting and write a summary note when…
project-with-reflect
Use project-with-reflect persistent project memory and reflection workflow.
jarvis-agent-rules
MCP server jarvis: notes, Jira, knowledge graph, sessions, preferences.