langchain

langchain is a cursor rule for Cursor from Bilal140202/the-lord-of-the-skills. It costs 511 tokens per session, scanned A, a copy of langchain, MIT.

A set of coding rules for LangChain, a framework for building applications that connect language models with prompts, tools, and multi-step workflows. The rules cover chains, prompts, agents, memory, tools, and tracing.

In plain words
What is it for?
Use it when writing or reviewing LangChain code, including prompt templates, chained steps, tool-using agents, parallel or batched work, output parsing, limits, and debugging traces.
Why use it?
It gives code assistants consistent patterns for structuring LangChain applications and helps avoid older or less suitable approaches.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Cursor.

Good fit Use it when writing or reviewing LangChain code, including prompt templates, chained steps, tool-using agents, parallel or batched work, output parsing, limits, and debugging traces.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/bilal140202/the-lord-of-the-skills/langchain
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skills

Made for: Cursor.

Wrote 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.

agentmods badge for langchain

README.md
[![agentmods](https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/langchain/github.svg)](https://agentmods.dev/rules/bilal140202/the-lord-of-the-skills/langchain)
Your own site
<a href="https://agentmods.dev/rules/bilal140202/the-lord-of-the-skills/langchain"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/langchain/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.

agentmods 80×15 button for langchain

Your own site · 80×15
<a href="https://agentmods.dev/rules/bilal140202/the-lord-of-the-skills/langchain"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/langchain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 511 This file is loaded in full into every session.
When invoked 511 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00511 $0.00511
Opus 5 $0.00255 $0.00255
Sonnet 5 $0.00102 $0.00102
Haiku 4.5 $0.00051 $0.00051

Measured 12d ago against content hash b777872e5592, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 12d 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.

Origin

This is a copy

100% identical to langchain — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/fangorn/cursor/nedcodes-ok__cursorrules-collection/langchain.mdc · 47 lines

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

Read the full file on GitHub · 47 lines

Changes

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.

  1. 12d ago First seen · 47 lines · 511 tokens per session scan A b777872e5592

Subscribe to this mod's changes

langchain is a cursor rule published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d 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. It is 100% identical to langchain, differing in 0 lines, and is treated as a copy.