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/sharrmavishal/operating-kit/code-changegit clone --depth 1 https://github.com/Sharrmavishal/operating-kitWhat 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.00218 | $0.00218 |
| Opus 5 | $0.00109 | $0.00109 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
code-change 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 2d 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
Code-change discipline (auto-attached when editing code)
Before any non-trivial edit, follow @docs/claude/vigilance-protocol.md:
- Re-read the whole function before each edit (state from a prior edit invalidates assumptions).
- Treat any reported bug as a hypothesis: read the code and write a verdict before fixing.
- 3 edits to one file = STOP: consolidate into one fix and state the invariant it preserves.
- Trace every write to every reader before changing a field's semantics.
Scan @docs/claude/field-notes.md before you deploy, migrate, gate a feature, or trust a build artifact. Those are the failures that pass every local test and surface in production.
Tune the
globsabove to this project's actual source directories/extensions.
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.
- 2d ago First seen · 19 lines · 218 tokens per session scan A 7fd34c9c01a4
code-change is a cursor rule published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 218 tokens to every session, about $0.0011 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
050-plan
When the user types /plan or asks to create a project plan, feature PRD, or retrospective.
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
execution
Repository execution and verification commands.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.
clean-code
Clean code principles for maintainable, readable, and well-structured code.
python
Python best practices with type hints, async patterns, and modern idioms.