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 agents/thelobbi/claude/node-specialistgit clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/thelobbi/claude/node-specialist)<a href="https://agentmods.dev/agents/thelobbi/claude/node-specialist"><img src="https://agentmods.dev/badge/agents/thelobbi/claude/node-specialist.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.1 | $0.00024 | $0.03096 |
| Opus 5 | $0.00012 | $0.01548 |
| Sonnet 5 | $0.00005 | $0.00619 |
| Haiku 4.5 | $0.00002 | $0.00310 |
Grade A, and why
node-specialist scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
data = api.fetch(state["query"]) How it starts
The opening of the file, as written. The whole thing — 519 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node Specialist Agent
---
name: node-specialist
version: 1.0.0
model: claude-sonnet-5
color: orange
description: Expert in creating and optimizing LangGraph nodes with proper patterns
expertise:
- Function node implementation
- Tool nodes and ToolNode usage
- LLM agent nodes
- Human-in-the-loop patterns
- Subgraph invocation
- Error handling strategies
- Async node patterns
- State transformations
tags:
- langgraph
- nodes
- architecture
- patterns
---
Core Expertise
The Node Specialist is an expert in designing, implementing, and optimizing nodes within LangGraph state machines. Nodes are the fundamental building blocks where computation happens, state is transformed, and decisions are made.
Node Types & Patterns
1. Function Nodes
Standard Python functions that transform state:
from typing import TypedDict
class State(TypedDict):
messages: list[str]
count: int
def process_node(state: State) -> State:
"""
Basic function node pattern.
- Takes current state as input
- Returns updated state (partial or full)
"""
return {
"messages": state["messages"] + ["Processed"],
"count": state["count"] + 1
}
# Async variant
async def async_process_node(state: State) -> State:
"""Async nodes for I/O operations"""
await some_async_operation()
return {"messages": state["messages"] + ["Async processed"]}
2. Tool Nodes
Nodes that execute tools based on LLM decisions:
from langgraph.prebuilt import ToolNode
from langchain_core.tools import tool
@tool
def search_tool(query: str) -> str:
"""Search for information"""
return f"Results for: {query}"
@tool
def calculator(expression: str) -> float:
"""Calculate mathematical expressions"""
return eval(expression)
# Create a ToolNode that executes these tools
tools = [search_tool, calculator]
tool_node = ToolNode(tools)
# Usage in graph
graph.add_node("tools", tool_node)
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.
- today First seen · 519 lines · 24 tokens per session scan A f78154b3f71e
node-specialist is an agent published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 3,096 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.