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/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/project-context)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/project-context"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/project-context/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/mhmdreza-rafiei/agent-tools/project-context"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/project-context.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.00432 | $0.00432 |
| Opus 5 | $0.00216 | $0.00216 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
project-context 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 8d 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
Project context
Keep shared context accurate so stateless agents stay aligned.
When this applies
The project has any of:
context/folderAGENTS.md,CLAUDE.md, orREADME.mdused as agent contextdocs/or other docs agents rely on for architecture, setup, or decisions
If none exist and the project is non-trivial, offer /groundwork to scaffold context.
Before work
- Read
AGENTS.mdif present. - Read relevant
context/files — start withoverview.mdandarchitecture.md. - Check
context/memory/progress.mdfor handoff state when resuming work.
After every task or action
Before you finish, update context when the task changed anything a future agent needs:
- Architecture, boundaries, folder structure, or data flow
- Standards, patterns, or conventions
- Plan, milestones, or decisions
- Dependencies, integrations, or build steps
- Current state, blockers, or follow-ups
Skip updates for trivial changes with no lasting impact (typos, comment-only edits, pure formatting).
How to update
| Target | Action |
|---|---|
context/ (any create, edit, add, delete) |
Read and follow the groundwork skill. Treat every change as /groundwork update: merge and improve — never make context thinner or vaguer. |
context/memory/progress.md |
Update for session handoff when work spans sessions or leaves follow-ups. |
| Other project docs | Update only affected files. Do not duplicate Build, Skills, or References outside AGENTS.md. |
Ground rules
- Verify against code before encoding — trust code over stale docs.
- Mark unverified claims as
> NEEDS VERIFICATION. - Preserve human edits; deepen and correct, do not clobber.
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.
- 8d ago First seen · 52 lines · 432 tokens per session scan A e3485061a6a7
project-context is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 24d ago), licensed MIT. It adds 432 tokens to every session, about $0.0022 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-09-03.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).