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/vohongtho/code-intel-platformWrote 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/vohongtho/code-intel-platform/code-intel)<a href="https://agentmods.dev/rules/vohongtho/code-intel-platform/code-intel"><img src="https://agentmods.dev/badge/rules/vohongtho/code-intel-platform/code-intel/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/vohongtho/code-intel-platform/code-intel"><img src="https://agentmods.dev/badge/rules/vohongtho/code-intel-platform/code-intel.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.02647 | $0.02647 |
| Opus 5.5 | $0.01059 | $0.01059 |
| Sonnet 5.5 | $0.00529 | $0.00529 |
| Haiku 4.5 | $0.00265 | $0.00265 |
Grade A, and why
code-intel 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- windsurfrules — 98% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-intel.mdc
Code Intelligence — code-intel-platform
⚠ This section is auto-managed by
code-intel analyze. Do not edit between the markers — your changes will be overwritten. Add your own notes below the<!-- code-intel:end -->marker.
FORBIDDEN: grep, rg, find, cat, sed, ls (for symbol/code discovery) REQUIRED BEFORE ANY CODE ACTION:
- code-intel search "" ← replaces grep/rg/find
- code-intel inspect ← replaces cat + manual file reading
- code-intel impact ← replaces manual caller tracing
Indexed: 6,254 nodes | 11,376 edges | 333 files | analyzed in 1.8s
Index stale? Re-run:
code-intel analyze
Mandatory Rules — ALL Agents (Amp, Claude Code, Codex, Copilot, Cursor, Aider, Gemini, Kiro, Trae, Hermes, Factory, OpenCode, Pi, Antigravity, OpenClaw, and others)
These rules apply to every coding agent or AI assistant working in this repository.
Before Implementing Any Change
- Run
code-intel search "<concept>"— find existing symbols related to the task. - Run
code-intel inspect <symbol>— understand callers, callees, and imports. - Run
code-intel impact <symbol>— check blast radius before touching anything. - If impact shows ≥ 5 direct callers → warn the user: HIGH risk.
While Implementing / Fixing a Bug
- NEVER open a file cold — always
code-intel searchfirst. - NEVER grep for symbols — use
code-intel searchinstead. - NEVER rename symbols with find-and-replace — use
code-intel inspectto find all usages first. - Use
code-intel inspect <symbol>to understand a function's callers/callees before modifying it. - Use
code-intel query "TRAVERSE CALLS FROM '<symbol>' DEPTH 3"to trace execution paths.
Before Committing / Code Review
- Run
code-intel impact <symbol>for every symbol you changed. - Run
code-intel pr-impact --base main --head HEADto see full PR blast radius. - Fail PR if HIGH risk symbols are changed without reviewer sign-off.
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 · 183 lines · 2,647 tokens per session scan A d95092eba184
code-intel is a cursor rule published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed 16d ago), licensed MIT. It adds 2,647 tokens to every session, about $0.0106 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-31.
Other cursor rules, from other repositories
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.