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/zethrise/codelookup-skill/codelookupgit clone --depth 1 https://github.com/ZethRise/CodeLookup-SkillWhat 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.00019 | $0.00258 |
| Opus 5 | $0.00010 | $0.00129 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
CodeLookup 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.
What it actually says
Always check impact before changing codebase. Code changes can break dependent systems. Follow this checklist.
Action Protocol
BEFORE editing, creating, or deleting code (functions, classes, files, variables, tables, config):
-
Run Dependency Pre-Check:
- Run workspace local
node bin/pre-check.js(or globalnpx codelookup-check/ localnpm run check) to scan Git changes, trace dependencies, and map the blast radius. - If
.codelookup/graph.jsondoes not exist or is outdated, runnode bin/generate-graph.jsfirst. - Always output the generated Mermaid blast radius flowchart in your response analysis.
- Run workspace local
-
Verify Callers:
- Inspect files identified by the pre-check tool.
- Trace contract, return type, schema, or signature changes.
-
Plan Cascade Updates:
- Ensure all affected callers and linked systems are modified in the same change step. No partial commits.
-
Run Integration Tests:
- Run tests covering both the modified file and its dependent files.
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 · 26 lines · 19 tokens per session scan A 3d4d213971df
CodeLookup is a cursor rule published in the GitHub repository ZethRise/CodeLookup-Skill (11 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 258 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
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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.