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/Sharrmavishal/operating-kitWrote 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/sharrmavishal/operating-kit/ship-and-recover)<a href="https://agentmods.dev/rules/sharrmavishal/operating-kit/ship-and-recover"><img src="https://agentmods.dev/badge/rules/sharrmavishal/operating-kit/ship-and-recover.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.00031 | $0.00243 |
| Opus 5 | $0.00015 | $0.00121 |
| Sonnet 5 | $0.00006 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
ship-and-recover 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
Ship & recover (apply when deploying or when prod breaks)
Deploying: test → build → deploy → verify-live. Confirm the live system actually reflects what you shipped (version/health endpoint, real behavior). "The deploy command exited 0" is not "it's live and serving the new code". Run a review pass before shipping.
Production incident: follow @docs/claude/incident-response.md in order: stabilize (stop the bleeding) → confirm the recovery point and state it → recover one change at a time → verify live → root-cause calmly → ship the mechanical fix (a gate, not a promise) → one-paragraph postmortem. A panicked fix-forward is what causes incident #2.
Anything touching crash paths, data, schema, auth, billing, or prod state is a pause-and-propose gate; see @docs/claude/multi-model-collaboration.md.
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 · 20 lines · 31 tokens per session scan A 5f9a20e729ae
ship-and-recover is a cursor rule published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 243 once invoked, about $0.0002 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-30.
Other cursor rules, from other repositories
nauro-adopt
Seeds Nauro's project store from an existing repo. Use after nauro adopt has run locally. On filesystem-capable surfaces, reads docs (README, manifests, ADRs, Memory-Bank) for rationale and inspects code, config, tests, lockfiles, and recent git history for evidence, then surfaces targeted probes that turn evidence…
nauro-context
Writes durable shared context into Nauro's project store so other agents (a later session or a parallel one) can discover and pull it, finds and reads context another agent left, or captures a resumable brief so your own next session in this environment picks up cleanly. Three modes. Author writes a shared brief for…
nauro-loop
Originate gated Delivery and Interview candidates, or coordinate selected Program Delivery as FRAME -> CHOOSE -> START -> ADVISE -> VERIFY -> ADVANCE. Human-named work bypasses candidate selection. Agent-originated work keeps read-only ORIENT, 1-3 candidates, mandatory human selection, reject-all, and no auto-pick…
nauro-interview
Ask compact, numbered prerequisite-ready questions to elicit tacit project reasoning or challenge a proposed choice against Nauro decisions and repository evidence. Continue until every material branch has a disposition, then classify the result as shared understanding without granting write authority. Use only when…
nauro-ship-task
Run the full planner -> executor -> reviewer -> tech-lead -> direct-user-confirm -> push chain through Cursor's native project workflow agents. Requires the four bundled .cursor/agents/nauro-.md definitions and fails closed without native dispatch.
execution
Repository execution and verification commands.