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 skills/graycodeai/starling/cursor-langchainnpx skills add GrayCodeAI/starling --skill cursor-langchaingit clone --depth 1 https://github.com/GrayCodeAI/starlingWhat 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.00010 | $0.00529 |
| Opus 5 | $0.00005 | $0.00264 |
| Sonnet 5 | $0.00002 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
cursor-langchain 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 yesterday.
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
LangChain Cursor Rules
You are an expert in LangChain development. Follow these rules:
Chains (LCEL)
- Use LangChain Expression Language (LCEL) with pipe operator: prompt | llm | parser
- Use RunnablePassthrough, RunnableParallel, RunnableLambda for chain composition
- Always end chains with an output parser: StrOutputParser, JsonOutputParser, PydanticOutputParser
- Use .with_config(run_name="...") for observability in LangSmith traces
- Use .batch() and .abatch() for parallel execution over multiple inputs
Prompts
- Use ChatPromptTemplate.from_messages() for chat models — never raw string formatting
- Use MessagesPlaceholder for dynamic message insertion (history, agent scratchpad)
- Keep system prompts in separate files or constants — not inline in chain definitions
- Use .partial() to pre-fill template variables at chain construction time
Agents
- Use create_tool_calling_agent() with tool-calling models — not legacy AgentExecutor patterns
- Define tools with @tool decorator — include docstrings (the LLM reads them)
- Set max_iterations on AgentExecutor to prevent infinite loops (default is too high)
- Use return_intermediate_steps=True for debugging and logging agent reasoning
Memory & History
- Use RunnableWithMessageHistory for conversation state — not ConversationBufferMemory (legacy)
- Store history in persistent backends (Redis, PostgreSQL) — not in-memory for production
- Trim history with trim_messages() to control context window usage
- Use ConversationSummaryMemory only when context window is a hard constraint
Retrieval (RAG)
- Use create_retrieval_chain() or LCEL with retriever | format_docs | prompt | llm
- Set search_kwargs={"k": 4} explicitly on retrievers — don't rely on defaults
- Use RecursiveCharacterTextSplitter with appropriate chunk_size and chunk_overlap
- Add metadata to documents at indexing time for filtered retrieval
Tools & Output
- Tools must have clear, concise descriptions — the model selects tools based on descriptions
- Use PydanticOutputParser with output_fixing_parser for structured LLM output
- Handle LLM errors with fallbacks: chain.with_fallbacks([fallback_chain])
- Use callbacks for streaming: chain.stream() or chain.astream() for real-time output
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.
- yesterday First seen · 50 lines · 10 tokens per session scan A 177c680abc89
cursor-langchain is a skill published in the GitHub repository GrayCodeAI/starling (2 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 529 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-31.
Other skills, from other repositories
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…
multi-bot
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be answered from the knowledge base first.
escalation
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is frustrated after repeated failures.
vfx-text-cursor
Cursor light trail, chromatic rays, and directional flares for word-by-word quote reveals in video intros.
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.