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/starter-series/mcp-server-starter/repo-contextgit clone --depth 1 https://github.com/starter-series/mcp-server-starterWrote 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/starter-series/mcp-server-starter/repo-context)<a href="https://agentmods.dev/rules/starter-series/mcp-server-starter/repo-context"><img src="https://agentmods.dev/badge/rules/starter-series/mcp-server-starter/repo-context.svg" alt="Measured on agentmods" 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.00080 | $0.00080 |
| Opus 5 | $0.00040 | $0.00040 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
repo-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 4d 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.
This is a copy
100% identical to repo-context — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Read AGENTS.md first. Treat it as the source of truth for this repo's
commands, invariants, public naming, release constraints, and first-user path.
This file is a thin client adapter for Cursor. Do not add independent strategy, roadmap, package-name, release, or baseline-scope rules here.
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.
- 4d ago First seen · 11 lines · 80 tokens per session scan A b14da0dbeb69
repo-context is a cursor rule published in the GitHub repository starter-series/mcp-server-starter (0 stars, last pushed 2d ago), licensed MIT. It adds 80 tokens to every session, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to repo-context, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
cursorrules
See CLAUDE.md for full context. Quick rules.
testing
Guide for writing pytest unit and integration tests.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
development-phase
开发阶段：以新代码清晰合理为先，兼容仅在零代价时顺带.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.