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/Consiliency/Code-Index-MCPWrote 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/consiliency/code-index-mcp/react)<a href="https://agentmods.dev/rules/consiliency/code-index-mcp/react"><img src="https://agentmods.dev/badge/rules/consiliency/code-index-mcp/react/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/consiliency/code-index-mcp/react"><img src="https://agentmods.dev/badge/rules/consiliency/code-index-mcp/react.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.02802 | $0.02802 |
| Opus 5.5 | $0.01121 | $0.01121 |
| Sonnet 5.5 | $0.00560 | $0.00560 |
| Haiku 4.5 | $0.00280 | $0.00280 |
Grade A, and why
react 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.
How it starts
The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Rules for Code-Index-MCP
Overview
This file defines React patterns and best practices for any future web UI components in the Code-Index-MCP project.
Component Structure
Functional Components with TypeScript
import React, { useState, useCallback, memo } from 'react';
interface CodeSearchProps {
onSearch: (query: string) => Promise<void>;
placeholder?: string;
className?: string;
}
export const CodeSearch = memo<CodeSearchProps>(({
onSearch,
placeholder = "Search code...",
className = ""
}) => {
const [query, setQuery] = useState('');
const [isSearching, setIsSearching] = useState(false);
const handleSearch = useCallback(async (e: React.FormEvent) => {
e.preventDefault();
if (!query.trim()) return;
setIsSearching(true);
try {
await onSearch(query);
} finally {
setIsSearching(false);
}
}, [query, onSearch]);
return (
<form onSubmit={handleSearch} className={className}>
<input
type="text"
value={query}
onChange={(e) => setQuery(e.target.value)}
placeholder={placeholder}
disabled={isSearching}
/>
<button type="submit" disabled={isSearching}>
{isSearching ? 'Searching...' : 'Search'}
</button>
</form>
);
});
CodeSearch.displayName = 'CodeSearch';
Custom Hooks
Data Fetching Hook
import { useState, useEffect, useCallback } from 'react';
interface UseApiOptions<T> {
initialData?: T;
onError?: (error: Error) => void;
}
function useApi<T>(
apiCall: () => Promise<T>,
options: UseApiOptions<T> = {}
) {
const [data, setData] = useState<T | undefined>(options.initialData);
const [loading, setLoading] = useState(false);
const [error, setError] = useState<Error | null>(null);
const execute = useCallback(async () => {
setLoading(true);
setError(null);
try {
const result = await apiCall();
setData(result);
return result;
} catch (err) {
const error = err instanceof Error ? err : new Error(String(err));
setError(error);
options.onError?.(error);
throw error;
} finally {
setLoading(false);
}
}, [apiCall, options.onError]);
return { data, loading, error, execute };
}
// Usage
function SymbolViewer({ symbolName }: { symbolName: string }) {
const { data, loading, error, execute } = useApi(
() => client.getSymbolDefinition(symbolName),
{ onError: (err) => console.error('Failed to load symbol:', err) }
);
useEffect(() => {
execute();
}, [execute]);
if (loading) return <div>Loading...</div>;
if (error) return <div>Error: {error.message}</div>;
if (!data) return null;
return <SymbolDetails symbol={data} />;
}
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 · 474 lines · 2,802 tokens per session scan A 9f9692ec8076
react is a cursor rule published in the GitHub repository Consiliency/Code-Index-MCP (59 stars, last pushed 4d ago), licensed MIT. It adds 2,802 tokens to every session, about $0.0112 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-30.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.