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/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/commands/thelobbi/claude/agent)<a href="https://agentmods.dev/commands/thelobbi/claude/agent"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/agent/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/commands/thelobbi/claude/agent"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/agent.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.00023 | $0.03412 |
| Opus 5.5 | $0.00009 | $0.01365 |
| Sonnet 5.5 | $0.00005 | $0.00682 |
| Haiku 4.5 | $0.00002 | $0.00341 |
Grade A, and why
lg:agent 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 1mo 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 — 580 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lg:agent - Agent Management
Manage agents in LangGraph projects including creating, modifying, and organizing multi-agent systems.
Workflow Steps
Add Agent
-
Validate Input
- Check project structure exists
- Verify agent name is unique
- Validate agent type
-
Generate Agent Code
- Create agent class/function
- Setup LLM configuration
- Add tool bindings
- Configure system prompt
-
Update Graph
- Add agent node to graph
- Setup routing logic
- Add conditional edges (if needed)
- Update state schema (if needed)
-
Generate Tests
- Create agent test file
- Add unit tests
- Add integration tests
-
Update Documentation
- Add agent to README
- Document agent capabilities
- Update architecture diagram
Remove Agent
-
Analyze Dependencies
- Find all references to agent
- Check for dependent edges
- Identify impacted routes
-
Remove Components
- Remove agent node from graph
- Remove agent file
- Clean up edges
- Update routing logic
-
Update Tests
- Remove agent tests
- Update integration tests
-
Update Documentation
- Remove from README
- Update architecture diagram
Modify Agent
-
Load Current Configuration
- Read agent definition
- Parse current settings
-
Apply Changes
- Update specified parameters
- Preserve unchanged settings
- Validate new configuration
-
Update Tests
- Adjust test cases
- Add new test coverage
-
Update Documentation
- Document changes
- Update examples
Agent Types
ReAct Agent
Reasoning and Acting pattern with tool use.
from langchain_anthropic import ChatAnthropic
from langgraph.prebuilt import create_react_agent
llm = ChatAnthropic(model="claude-sonnet-5")
agent = create_react_agent(
llm,
tools=tools,
state_modifier="You are a helpful assistant."
)
Tool-Calling Agent
Optimized for structured tool usage.
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.
- 1mo ago First seen · 580 lines · 23 tokens per session scan A a2ae5465baa3
lg:agent is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 3,412 once invoked, about $0.0001 per session on Opus 5.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-05.
Other commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
session
Complete guide to managing pair programming sessions.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
story-and-test
For the component(s) in scope.