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/project-contextgit 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.00343 | $0.00343 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
project-context scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
post-change live curl/query; consumer-route audit after an API/shape change; verify any What it actually says
{{PROJECT_NAME}}: project context
Template. Fill every
{{PLACEHOLDER}}from THIS codebase (the bootstrap does this by exploring the repo). The stable method is in @.cursor/rules/operating-method.mdc.
What this project is
{{One-paragraph description: what it does, who it's for, current state. Replace this block.}}
Stack
{{Languages, frameworks, DB, infra, key services. Where secrets live (and that they're never committed). Any non-obvious build/deploy step.}}
Coding standards
{{Project conventions. Examples: error-handling norms; no hardcoded secrets + maintain .env.example; destructive ops only via the approved safe path; one logical change per commit; honest user-facing positioning.}}
Pre-ship gates
{{Each gate = a live check returning a count with an explicit pass condition. Seed: post-change live curl/query; consumer-route audit after an API/shape change; verify any hardcoded threshold against a live distribution before shipping.}}
Locked decisions: do not relitigate
Rule: if a new idea conflicts with a decision below, report it as a deferred option; do not implement by default. "Looks ready" is not the trigger; the documented condition must be met.
- (none yet)
Open work
- (none yet)
Quick reference
{{Common commands: build, test, run, inspect data, deploy.}}
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 · 39 lines · 343 tokens per session scan A df6a654eb632
project-context is a cursor rule published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 343 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
minimax-m3-status-verification
MiniMax M3 status and verification contract: exact claim labels, proof matching, multimodal-grounded visual claims, and evidence-first closeouts.
testing
Testing rules for vitest suite.
execution
Repository execution and verification commands.
project-overview
Project overview and conventions for the Idun Agent Platform monorepo.
cursorrules
Cursor rule "cursorrules" from evolution-foundation/evo-ai, covering evo ai - project rules and structure, main technologies, project structure, code standards and language requirements.