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/srmackey/insituWrote 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/srmackey/insitu/cursor)<a href="https://agentmods.dev/rules/srmackey/insitu/cursor"><img src="https://agentmods.dev/badge/rules/srmackey/insitu/cursor/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/srmackey/insitu/cursor"><img src="https://agentmods.dev/badge/rules/srmackey/insitu/cursor.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.00591 | $0.00591 |
| Opus 5.5 | $0.00236 | $0.00236 |
| Sonnet 5.5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
cursor 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 1mo 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
Insitu router
Insitu stores reusable articles and composes a project protocol. The project key is the working folder basename (projects/<folder>/).
The composed core lives in this checkout as PROTOCOL.md and as the host protocol file under .cursor/rules/insitu-protocol.mdc. Treat that generated pack as binding. Do not edit it.
If the pack is missing, or its header is stale relative to the vault, call materialize (or resolve_protocol then materialize) before other work.
materialize writes only that generated pack. It never writes AGENTS.md or CLAUDE.md. If other host files this host loads are missing, retrieve the multi-platform pack (get_article platform/router-vs-pack and platform/cursor) and write them here. Do not put pack bodies in this router. If those articles miss, the pack is not installed; say so. Do not invent files the pack does not name.
If the user asks Insitu status of this folder, call project_status. Do not walk get_project, resolve_protocol, or get_role for that readout. Do not call it at session start.
Pull on-demand articles with get_article when the work needs one.
Do not pull the on-demand list at session start.
Use list_articles to see the catalog and sizes (what to include, what to trim).
Do not call it at session start to load the core.
Mapped skills are generated copies under the host skill directories
(.grok/skills, .claude/skills, .cursor/skills). Treat them as binding
for /name. Do not edit them.
If a generated skill is missing or its stamp is stale relative to the
vault, call materialize.
Pull a skill body for inspect with get_skill. Use list_skills to see
the catalog and sizes (what to attach). Do not call list_skills at
session start to load skills. Host discovery is the load path.
After an authoring write, if this working folder's project key is in affects_projects:
- Call
materializeon this checkout. - Tell the user the loaded protocol is stale and they should start a new session.
- Do not continue as if the new article or role is already in core.
If this project is not in the list, keep working.
Do not call delete_article, delete_role, delete_project, or delete_skill unless the user explicitly asked to delete that object. Do not treat validate findings as a reason to delete. Never clean up the vault.
This router is not the protocol. It does not contain project-specific guidance.
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.
- 1mo ago Changed · -7 tokens per session 3c4bec25e0b9
- 1mo ago First seen · 43 lines · 598 tokens per session scan A f7d2c0eccada
cursor is a cursor rule published in the GitHub repository srmackey/insitu (0 stars, last pushed 8d ago), licensed MIT. It adds 591 tokens to every session, about $0.0024 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.