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/brainy-builds/ts-inspect-cli/scip-toolsgit clone --depth 1 https://github.com/Brainy-Builds/ts-inspect-cliWhat 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.07610 | $0.07610 |
| Opus 5 | $0.03805 | $0.03805 |
| Sonnet 5 | $0.01522 | $0.01522 |
| Haiku 4.5 | $0.00761 | $0.00761 |
Grade A, and why
scip-tools 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.
bash -c 'curl -L "https://github.com/scip-code/scip/releases/download/$TAG/scip-$OS-$ARCH.tar.gz"' \ How it starts
The opening of the file, as written. The whole thing — 622 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCIP Code Intelligence for AI Agents
Purpose
AI LLM agents working on this codebase lack a built-in language server. SCIP (Semantic Code Intelligence Protocol) fills that gap. A SCIP index of the codebase is stored as a compact binary file. The scip CLI and a language-specific indexer (for this repo, scip-typescript) let an agent look up symbol definitions, find references, inspect type signatures, and navigate code semantically - the same operations an IDE performs with a language server - using only shell commands.
Use SCIP whenever you need to understand where a symbol is defined, who references it, what its type signature is, or how a file's symbols are structured - especially before refactoring, renaming, or auditing against the Code Rules. SCIP queries are precise (indexed by symbol), fast, and avoid the context cost of reading large files. Prefer SCIP over grep for any question that is fundamentally about a symbol, a type, a reference, or a file's structure.
When to Use - PREFER SCIP OVER GREP
Reach for SCIP, not grep, when any of the following are true. These are semantic questions; a text search cannot answer them reliably. Text search finds the string, not the symbol - it misses aliases, re-exports, shadowing, imports, and type-only usages, and it returns every comment and string literal that happens to contain the name.
| You are about to... | Use SCIP instead of grep because |
|---|---|
| Rename a symbol (function, variable, type, interface, class, constant) | grep finds the substring everywhere; SCIP returns every reference and the single definition, with line numbers and roles. |
| Find all usages of a symbol before changing its signature | grep misses aliased imports (import { foo as bar }) and re-exports; SCIP follows the symbol identity. |
| Check whether a symbol is defined in the right place per Code Rules | grep cannot tell definition from reference; SCIP role=1 pinpoints the definition file. |
| Inspect a symbol's type signature or JSDoc without opening the file | grep cannot return a signature; SCIP returns the documentation array with the signature and JSDoc. |
| List what a file exports / defines | grep on export misses export { x } blocks and re-exports; SCIP lists every defined symbol precisely. |
| Find every file that imports a given module's symbols | grep on the module path misses aliased and type-only imports; SCIP role=0 on the exported symbols finds them all. |
Audit for symbols defined outside their required directory (e.g. interface outside ./src/types/**) |
grep cannot correlate "is an interface" with "is outside src/types/"; SCIP filters by symbol kind AND path in one query. |
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 · 622 lines · 7,610 tokens per session scan A 7d1aa635a00a
scip-tools is a cursor rule published in the GitHub repository Brainy-Builds/ts-inspect-cli (2 stars, last pushed 13d ago), licensed MIT. It adds 7,610 tokens to every session, about $0.0381 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-31.
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.