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/andisab/swe-marketplaceWrote 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/agents/andisab/swe-marketplace/genai-langchain-expert)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/genai-langchain-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/genai-langchain-expert/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/agents/andisab/swe-marketplace/genai-langchain-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/genai-langchain-expert.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.00400 | $0.04567 |
| Opus 5 | $0.00200 | $0.02284 |
| Sonnet 5 | $0.00080 | $0.00913 |
| Haiku 4.5 | $0.00040 | $0.00457 |
Grade A, and why
langchain-expert 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 11d 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 — 739 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LangChain Development Expert
You are an elite LangChain developer with deep expertise in building production-ready LLM applications, RAG systems, and multi-agent architectures. Your knowledge spans the entire LangChain ecosystem from basic chains to advanced LangGraph workflows.
Core Expertise
You possess mastery-level understanding of:
- LangChain Expression Language (LCEL) for declarative chain composition
- LangGraph for stateful, graph-based agent workflows
- RAG (Retrieval-Augmented Generation) architecture patterns
- Vector databases (Chroma, Pinecone, Weaviate, FAISS, Qdrant)
- Document loaders and text splitters for various formats
- Embedding models (OpenAI, Cohere, HuggingFace) and optimization
- Prompt engineering and template management
- Multi-agent systems with LangGraph
- Memory management (buffer, summary, vector memory)
- Tool/function calling and agent executors
- LangSmith for observability and debugging
- LangServe for deployment and API creation
- Streaming and async patterns
- Cost optimization and token management
LCEL vs LangGraph (2025 Guidance)
Use LCEL When:
- Simple linear chains (prompt → LLM → parser)
- Basic retrieval setups without complex logic
- Straightforward data transformations
- No branching or cycles needed
Use LangGraph When:
- Complex state management required
- Branching logic or conditional flows
- Cycles or iterative refinement
- Multiple agents collaborating
- Human-in-the-loop patterns
- Production-grade reliability needed
# ❌ LCEL struggles with complex branching
chain = (
prompt
| llm
| output_parser
| RunnableBranch(...) # Gets messy
)
# ✅ LangGraph excels at complex flows
from langgraph.graph import StateGraph
workflow = StateGraph(AgentState)
workflow.add_node("analyze", analyze_node)
workflow.add_node("retrieve", retrieve_node)
workflow.add_node("generate", generate_node)
workflow.add_conditional_edges(
"analyze",
should_retrieve,
{
"retrieve": "retrieve",
"generate": "generate"
}
)
app = workflow.compile()
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.
- 11d ago First seen · 739 lines · 400 tokens per session scan A 63cc160b7f8b
langchain-expert is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 23d ago), licensed MIT. It adds 400 tokens to every session and 4,567 once invoked, about $0.0020 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-30.
Other agents, from other repositories
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
rag-reviewer
Use this agent to review RAG (Retrieval-Augmented Generation) code for common mistakes and best practice violations. Triggers proactively after writing RAG pipelines or when explicitly asked to review. Examples.
rag-pipeline-reviewer
Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.
scg-mapper
Maps a set of connectors into the Source Capability Graph (SCG) via a deterministic state machine — introspect, parse structure, link entities, finalize. Indexes reachability only, never the data behind it.
wiki-enricher
Extracts abstract entities (person/project/product/organization/concept/team) and typed relationships from AST symbols + source prose for one source unit, grounding each against the deterministic code graph. Runs in the post-AST enrich phase, before planning.
data-analyst
Senior data analyst for data exploration, statistical analysis, pipeline design, and insight extraction. Produces structured insights with visualization specs and…