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/mdc-langchainnpx skills add GrayCodeAI/starling --skill mdc-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.00040 | $0.02506 |
| Opus 5 | $0.00020 | $0.01253 |
| Sonnet 5 | $0.00008 | $0.00501 |
| Haiku 4.5 | $0.00004 | $0.00251 |
Grade A, and why
mdc-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 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.
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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LangChain Best Practices
This guide outlines the definitive best practices for developing with LangChain. Adhere to these rules to ensure your LLM applications are modular, scalable, and production-ready.
1. Code Organization and Structure
Always structure your LangChain projects around core components, separating concerns into distinct modules. This enhances readability, testability, and maintainability.
✅ GOOD: Modular Structure Organize by component type (models, prompts, tools, agents, memory).
# my_project/
# ├── agents/
# │ └── flight_booking_agent.py
# ├── models/
# │ └── llm_config.py
# ├── prompts/
# │ └── flight_prompts.py
# ├── tools/
# │ └── flight_tools.py
# ├── memory/
# │ └── chat_memory.py
# └── main.py
❌ BAD: Monolithic Files Avoid dumping all logic into a single file.
# main.py (containing everything)
from langchain_openai import ChatOpenAI
from langchain_core.prompts import ChatPromptTemplate
# ... many more imports and definitions
# ... LLM, prompt, tools, agent definition all in one file
2. Leverage LangChain Expression Language (LCEL)
LCEL is the modern, recommended way to compose chains. It offers first-class streaming, async support, and clear debugging. Never use deprecated LLMChain or older chain patterns.
✅ GOOD: LCEL for Chains
Use the | operator for clear, composable pipelines.
from langchain_core.prompts import ChatPromptTemplate
from langchain_openai import ChatOpenAI
from langchain_core.output_parsers import StrOutputParser
# Define components
prompt = ChatPromptTemplate.from_messages([
("system", "You are a helpful assistant."),
("user", "{question}")
])
llm = ChatOpenAI(model="gpt-4o-mini", temperature=0)
output_parser = StrOutputParser()
# Compose chain with LCEL
chain = prompt | llm | output_parser
# Invoke
response = chain.invoke({"question": "What is the capital of France?"})
print(response)
❌ BAD: Deprecated LLMChain
This pattern is outdated and lacks modern features.
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 · 327 lines · 40 tokens per session scan A 4e87c5a82696
mdc-langchain is a skill published in the GitHub repository GrayCodeAI/starling (2 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 2,506 once invoked, about $0.0002 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
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
security-review
Review trust boundaries, auth/authz, injection, secrets, filesystem/network exposure, dependencies, and exploitability without pretending a shallow lint is an audit.
coding
编写并运行 Python 代码,验证脚本逻辑和输出。.