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/nedcodes-ok/cursorrules-collection/langchaingit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/langchain)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/langchain"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/langchain.svg" alt="Measured on agentmods" 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 | $0.00511 | $0.00511 |
| Opus 5 | $0.00255 | $0.00255 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- langchain — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 · 47 lines · 511 tokens per session scan A b777872e5592
langchain is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 511 tokens to every session, about $0.0026 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-09-03.
Other cursor rules, from other repositories
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
03-ui
UI, layout, theming and localization standards.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.
01-tech-stack
Android tech stack and project standards.