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/kanevry/session-orchestrator/040-discoverygit clone --depth 1 https://github.com/Kanevry/session-orchestratorWrote 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/kanevry/session-orchestrator/040-discovery)<a href="https://agentmods.dev/rules/kanevry/session-orchestrator/040-discovery"><img src="https://agentmods.dev/badge/rules/kanevry/session-orchestrator/040-discovery.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 | $0.00018 | $0.02437 |
| Opus 5 | $0.00009 | $0.01218 |
| Sonnet 5 | $0.00004 | $0.00487 |
| Haiku 4.5 | $0.00002 | $0.00244 |
Grade A, and why
040-discovery 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery — Quality Analysis & Issue Detection
Systematic quality discovery that runs modular probes adapted to the project's tech stack, presents findings interactively, and creates VCS issues for confirmed problems.
Invocation
- Standalone (
/discovery [scope]): Full flow with interactive triage (Phases 0-5 + Phase 6 stats) - Embedded (from session-end when
discovery-on-close: true): Phases 0-3 only, returns structured JSON to caller
Scope accepts: all (default), code, infra, ui, arch, session, audit, vault, feature, or comma-separated like code,session.
Phase 0: Read Session Config
Read Session Config from CLAUDE.md. Parse discovery-specific fields:
discovery-probes,discovery-exclude-paths,discovery-severity-threshold,discovery-confidence-threshold,discovery-on-close
Phase 1: Stack Detection
Detect the project's tech stack via marker file checks (Glob):
| Marker File(s) | Activates |
|---|---|
package.json |
JS/TS probes |
tsconfig.json |
TypeScript probes |
requirements.txt / pyproject.toml |
Python probes |
Dockerfile / docker-compose.yml |
Container probes |
.github/workflows/ |
GitHub CI probes |
.gitlab-ci.yml |
GitLab CI probes |
next.config.* / nuxt.config.* |
SSR probes |
tailwind.config.* |
Tailwind probes |
.orchestrator/ exists |
Session probes |
Build activation set: start with marker-matched probes → intersect discovery-probes config (if set) → restrict to scope argument (if passed).
Default exclude paths (always apply): node_modules/, .git/, dist/, build/, .next/, .nuxt/, coverage/. Add paths from discovery-exclude-paths.
Report: "Discovery: [N] probes active across [categories]. Stack: [detected]. Threshold: [severity]."
Phase 2: Probe Execution
Run probes sequentially — Cursor has no parallel agents. One category at a time. Complete each category's analysis before moving to the next.
6 Probe Categories
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.
- 3d ago First seen · 243 lines · 18 tokens per session scan A 70eca8fa8903
040-discovery is a cursor rule published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 2,437 once invoked, about $0.0001 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
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
kandev-pr-fixup
Kandev PR fixup workflow prompt for Cursor agents.
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.
cli-error-handling
CLI command error handling patterns.