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/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/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/starter-series/mcp-server-starter/repo-context"><img src="https://agentmods.dev/badge/rules/starter-series/mcp-server-starter/repo-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.00080 | $0.00080 |
| Opus 5.5 | $0.00032 | $0.00032 |
| Sonnet 5.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 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.
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.
- 2mo 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 yesterday), licensed MIT. It adds 80 tokens to every session, about $0.0003 per session on Opus 5.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
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.
vibes-plug-devops
Vibes-Plug Cloud & DevOps Platform Engineering — Docker BuildKit, distroless runtimes, Kubernetes GitOps, and GitHub Actions OIDC.
ci-cd-workflows
This rule provides guidance on the CI/CD pipeline, GitHub Actions workflows (defined in .github/workflows/), custom actions (in .github/actions/), versioning strategies, and release processes. Use this rule if the query involves CI/CD, build/test issues, release procedures, versioning questions, or if it references…