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/readmegit 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/readme)<a href="https://agentmods.dev/agents/thelobbi/claude/readme"><img src="https://agentmods.dev/badge/agents/thelobbi/claude/readme.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 | $0.00000 | $0.01555 |
| Opus 5 | $0.00000 | $0.00777 |
| Sonnet 5 | $0.00000 | $0.00311 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
README 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent System
The agent system provides 137 specialized subagents that Claude invokes using the
Task tool. Each agent is a markdown file with a YAML frontmatter block (or embedded
YAML section) that declares its name, model, tools, and purpose. Agents are organized
into domain-specific directories so they are easy to find and extend.
Why agents instead of one general assistant
A single general-purpose assistant accumulates context and loses precision on
specialized tasks. Agents isolate concerns: a k8s-debugger knows Kubernetes
deeply and nothing else, which keeps its instructions tight and its output reliable.
The master orchestrators (angelos-symbo, ultrathink) handle decomposition and
delegation — specialized agents handle execution.
Agent file format
---
name: agent-name
description: One-line description. Tells Claude when to invoke this agent.
tools: Read, Grep, Glob, Bash, Write, Edit
model: sonnet
memory: project
---
You are a [role]. [System prompt defining behavior, checklist, output format...]
Some agents use an embedded YAML block instead of frontmatter:
# Agent Title
## Agent Metadata
\`\`\`yaml
name: agent-name
model: opus
category: orchestration
keywords:
- keyword1
- keyword2
\`\`\`
The description field (or the keywords list) is what Claude reads to decide
whether to invoke this agent. Write descriptions as "use this when..." phrases.
Top-level core agents (8)
These eight agents live directly in agents/ and are the most broadly applicable.
They are proactively invoked across all domains.
| Agent | Model | Purpose |
|---|---|---|
code-reviewer |
sonnet | Post-write code review: security, type safety, error handling, N+1 queries |
debugger |
sonnet | Systematic debugging: reproduce, isolate, fix, regression-test |
doc-writer |
haiku | Documentation for code, APIs, and architecture |
docker-ops |
haiku | Docker build, push, compose, multi-stage image management |
k8s-image-auditor |
sonnet | Audits K8s deployments for stale images and pull policy misconfigurations |
researcher |
haiku | Fast lookup and web research via MCP tools |
security-reviewer |
sonnet | Security audit: injection, secrets exposure, auth flaws, dependency CVEs |
test-writer |
sonnet | Test generation: unit, integration, edge cases, regression tests |
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 · 131 lines · 0 tokens per session scan A 7425881ff9f2
README is an agent published in the GitHub repository TheLobbi/claude (21 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,555 tokens. 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.