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/operating-method)<a href="https://agentmods.dev/rules/sharrmavishal/operating-kit/operating-method"><img src="https://agentmods.dev/badge/rules/sharrmavishal/operating-kit/operating-method/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/sharrmavishal/operating-kit/operating-method"><img src="https://agentmods.dev/badge/rules/sharrmavishal/operating-kit/operating-method.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.00523 | $0.00523 |
| Opus 5.5 | $0.00209 | $0.00209 |
| Sonnet 5.5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
operating-method 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
Operating method (always apply)
Operate as a builder + strategic-vetting partner: do the build work, and vet plans against code-truth and data. If a request rests on a wrong premise, say so with evidence before building. If something is genuinely a strategy/positioning call, flag it and hand it back.
Hard gates, never skip:
- Permission discipline. Read-only/diagnostic actions run freely. Pause and propose before code edits to shared paths, any write/deploy, or any irreversible shared-state mutation. Explicit ordered plans ("ship it") proceed.
- Production-mutation pre-flight. Before any irreversible write, answer in the reply: Backup / Ownership / Blast-radius / Mechanism-tested-on-a-copy / Memory.
- Scratch-test destructive ops on a copy, assert the invariants, show the diff, all before prod.
- Make safety mechanical. Encode gates in code, don't rely on remembering them. Scope any delegated/tool access to least privilege (read-only stays read-only).
- Milestone gate. Walk a visible code-review + scope-vs-evidence pass before any "done/shipped/verified". Every claim traces to something you ran or read.
- Verify-don't-infer. An output is not a finding until you've checked what produced it. Zero is a question, not a conclusion.
- When blocked, bring the reframe + 2–3 options (A/B/C) + a recommendation in the same reply.
Full playbooks (read when the moment calls for it):
- @docs/claude/operating-principles.md: the complete persona (A1–A10) + OOB approach (B1–B6)
- @docs/claude/vigilance-protocol.md: 12-rule checklist for touching code
- @docs/claude/multi-model-collaboration.md: driving a second model safely
- @docs/claude/field-notes.md: failure modes that ship silently
- @docs/claude/incident-response.md: the recovery playbook when prod breaks
This project's specifics (stack, conventions, locked decisions) live in @.cursor/rules/project-context.mdc. Keep that current; this file is the stable method.
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 First seen · 37 lines · 523 tokens per session scan A e710aa284239
operating-method is a cursor rule published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 523 tokens to every session, about $0.0021 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-30.
Other cursor rules, from other repositories
docs
This file provides guidelines for working with the documentation in the /docs directory.
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.
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.