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/srmackey/insitu/cursorgit clone --depth 1 https://github.com/srmackey/insituWhat 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 | $0.00598 | $0.00598 |
| Opus 5 | $0.00299 | $0.00299 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
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 today.
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 stanzas 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_stanza platform/router-vs-pack and platform/cursor) and write them here. Do not put pack bodies in this router. If those stanzas 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 stanzas with get_stanza when the work needs one.
Do not pull the on-demand list at session start.
Use list_stanzas 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 stanza or role is already in core.
If this project is not in the list, keep working.
Do not call delete_stanza, 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.
- today 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 yesterday), licensed MIT. It adds 598 tokens to every session, about $0.0030 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-08-31.
Other cursor rules, from other repositories
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.
cursorrules
This is an MCP (Model Context Protocol) server that provides Notion integration tools and AI agent workflows. Built with TypeScript, using the MCP SDK for server implementation.
lighter-safety
Safety contract for the Lighter MCP server. Apply whenever a lighter tool is invoked.
nix-security
Nix Security and Sandboxing.
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…